Aegis MCP server
{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}{
"servers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx agent-aegisversion 0.1.6
What it does
Aegis is a governance layer for AI agents that provides policy-based control over tool calls across 12 agent frameworks through a single unified API. It enforces governance primitives like prompt-injection blocking, PII masking, policy enforcement, trust delegation, and audit logging without requiring code changes to agent implementations.
- Define YAML policies once and apply them uniformly across LangChain, CrewAI, OpenAI Agents, and other supported frameworks without modifying agent code.
- Block tool calls that violate security policies, mask sensitive data, and enforce rate limits or cost budgets across all agent invocations.
- Generate tamper-evident audit logs of agent actions, including delegation chains and justification gaps, for compliance and security review.
Tools this server exposes
| Tool | Does |
|---|---|
| auto_instrument | Automatically instruments installed agent frameworks with governance hooks in a single call. |
| Policy | Declarative YAML-based rules engine that matches tool calls and applies risk-based approvals. |
| Action | Unified representation of tool, LLM, HTTP, or MCP calls across all supported frameworks. |
| ActionClaim | Tripartite structure capturing declared intent, Aegis-assessed properties, and delegation chains. |
| Guardrails | Deterministic checks for prompt injection, PII, and other security patterns. |
| AuditEvent | Tamper-evident audit trail of agent actions and governance decisions. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.