MCPGuard — Security Gateway for AI Agent Tool Calls
Open-source MCP/A2A proxy that policy-enforces, taint-tracks, sandboxes, and audit-logs every AI agent tool call. OWASP ASI 2026 compliant.
Why MCPGuard?
AI agents (LangChain, CrewAI, AutoGen, Copilot) call tools autonomously — reading files, executing code, making HTTP requests. Without a security layer, a single prompt injection can exfiltrate secrets, overwrite critical files, or run arbitrary code.
MCPGuard is the missing chokepoint. It sits between your agent and MCP tool servers, enforcing security policies on every single call:
┌─────────────┐ ┌──────────────────────────┐ ┌─────────────┐
│ AI Agent │────▶│ MCPGuard │────▶│ MCP Tool │
│ (LangChain, │◀────│ Security Gateway │◀────│ Server │
│ CrewAI, etc) │ └──────────────────────────┘ └─────────────┘
└─────────────┘ │ Policy │ Taint │ Sandbox │
│ DEE │ Audit │ eBPF │
What happens to every tool call:
| Step | What MCPGuard Does |
|---|---|
| 1. Policy Check | Evaluates against YAML rules with OWASP ASI 2026 mappings — blocks or allows |
| 2. Taint Scan | Detects secrets (AWS keys, JWTs), PII (SSN, credit cards), and user input in arguments |
| 3. Sandbox Execution | Runs code in Docker, Firecracker, WASM, or Microsandbox — never on bare metal |
| 4. Deterministic Envelope | Hashes inputs/outputs, Sigstore-signs the trace — fully replayable |
| 5. Audit Log | Writes to tamper-proof append-only log with SIEM export (CEF, JSONL, CSV) |
Features
- YAML Policy Engine — define allow/deny/audit/sandbox rules per tool, argument pattern, or taint label
- Taint Tracking — automatic detection of secrets, PII, API keys, JWTs in tool call arguments
- 4 Sandbox Backends — Docker, Firecracker microVMs, WASM, Microsandbox
- Deterministic Execution Envelopes (DEE) — every execution is hashed and Sigstore-signed for replay
- OWASP ASI 2026 Compliance — built-in policy sets mapping to ASI-01 through ASI-08
- Append-Only Audit Logs — SQLite-backed, content-hashed, with CEF/JSONL/CSV SIEM export
- Kong-Style Plugin Pipeline —
pre_execution → execution → post_execution → logwith priorities - Rate Limiting — per-identity token bucket with LRU eviction
- Prometheus Metrics + OpenTelemetry — full observability out of the box
- Optional eBPF Probes — kernel-level syscall monitoring at MCP boundaries
Quick Start
# Install
pip install -e "."
# Initialize config and policies
mcpguard init
# Start the security gateway
mcpguard serve --host 127.0.0.1 --port 8000
Point your MCP client to http://localhost:8000/mcp instead of targeting tool servers directly.
Use Cases
| Scenario | How MCPGuard Helps |
|---|---|
| AI Coding Assistants | Intercepts Copilot/Cursor tool calls, blocks dangerous file writes, prevents secret exfiltration |
| Autonomous Agents | Policy-enforces LangChain/CrewAI/AutoGen tool usage, sandboxes code execution |
| Enterprise MCP Deployments | OWASP ASI compliance, tamper-proof audit trails, SIEM integration |
| Research Reproducibility | Deterministic execution envelopes — every result is signed and replayable |
| Multi-Agent Workflows | Cross-tool taint tracking — PII in one tool's output can't leak to another's HTTP call |
| Regulated Industries | Append-only audit logs, integrity verification, CEF export for security teams |
Architecture
src/mcpguard/
├── proxy/ # FastAPI MCP/A2A gateway — auth, rate limiting, plugin pipeline
├── policy/ # YAML rule engine with OWASP ASI 2026 mappings
├── taint/ # Source/sink taint tracking — secrets, PII, user input detection
├── sandbox/ # Docker, Firecracker, WASM, Microsandbox execution backends
├── dee/ # Deterministic Execution Envelopes — hash, sign, replay, drift detect
├── audit/ # Append-only Sigstore-signed audit logs + SIEM export
├── context/ # Token-efficient context reduction via TF-IDF + AST pruning
├── ebpf/ # Optional kernel-level syscall monitoring (BCC probes)
├── observability/ # Prometheus metrics, OpenTelemetry tracing, health checks
├── config.py # Pydantic v2 hierarchical config (YAML → env → CLI)
├── cli.py # Typer CLI — serve, scan, replay, audit, init
└── utils.py # Hashing, exceptions, structured logging
Policy Rules
MCPGuard ships with three policy sets:
owasp_asi_2026_strict.yaml— Full OWASP ASI 2026 coverage (ASI-01 through ASI-08)minimal.yaml— Lightweight defaults for developmentcustom_template.yaml— Copy and customize for your environment
Example rule:
rules:
- id: ASI-03-001
name: Block PII in outbound calls
description: Prevent PII-tainted data from reaching HTTP sinks
action: deny
priority: 10
tool_patterns:
- "http_post"
- "send_email"
taint_labels:
- pii
- secret
owasp_asi_id: ASI-03
CLI Reference
| Command | Description |
|---|---|
mcpguard serve |
Start the proxy gateway |
mcpguard init |
Initialize config and policies in a project |
mcpguard scan <file> |
Static taint analysis on Python code |
mcpguard validate-policy <path> |
Validate policy YAML files |
mcpguard trace-list |
List recent execution traces |
mcpguard trace-export <id> |
Export a trace as JSON |
mcpguard replay <id> |
Replay a trace and check for drift |
mcpguard audit-query |
Query audit logs with filters |
mcpguard audit-verify |
Verify audit log integrity |
mcpguard config-show |
Show effective configuration |
Configuration
Config loads hierarchically: YAML → environment variables → CLI flags.
# .mcpguard/config.yaml
proxy:
host: 127.0.0.1
port: 8000
sandbox:
backend: docker # docker | firecracker | wasm | microsandbox
timeout_seconds: 30
taint:
mode: hybrid # decorator | ebpf | hybrid | disabled
policy:
default_action: deny # deny-by-default for production
policy_paths:
- policies/owasp_asi_2026_strict.yaml
observability:
log_level: info
metrics_enabled: true
otlp_endpoint: "" # Set for OpenTelemetry export
Environment variable override: MCPGUARD_SANDBOX__BACKEND=wasm
Docker Deployment
# Build and run
docker compose up -d
# With Prometheus monitoring
docker compose --profile monitoring up -d
Development
# Clone and install
git clone https://github.com/piyushptiwari1/mcpguard.git
cd mcpguard
pip install -e ".[dev]"
# Run tests (173 tests)
pytest tests/ -v --cov=mcpguard
# Lint
ruff check src/ tests/
ruff format src/ tests/
Examples
Integration examples for popular AI agent frameworks:
- LangChain — route LangChain tool calls through MCPGuard
- CrewAI — secure CrewAI agent tool usage
- AutoGen — protect AutoGen multi-agent conversations
- Copilot Guard — intercept Copilot/Cursor tool calls
Contributing
See CONTRIBUTING.md for development setup, testing, and PR guidelines.
License
Apache 2.0 — see LICENSE.