Secure Agent MCP Gateway
Secure Agent MCP Gateway
SOC-Alert-Triage mit einem MCP-zu-MCP-Sicherheitsgateway: Der Agent
kommuniziert nie direkt mit echten Tools. Jeder tools/list- / tools/call-Aufruf
wird anhand der Rolle (viewer | operator | admin) eingeschränkt und autorisiert.
main.py (agent) → gateway → mcp_server (tools)Weitere Details: gateway/README.md.
Schnellstart (lokal)
python -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
cp .env.example .env
# edit .env — set LLM_API_KEY (never commit .env)Drei Rollen-Dienste (lokal)
# 1) Viewer — reputation lookups only
python main.py --mcp --role viewer --alert sample_alert.json
# 2) Operator — triage / summarize / notify (no block or escalate)
python main.py --mcp --role operator --alert sample_alert.json
# 3) Admin — full tool set through the gateway
python main.py --mcp --role admin --alert sample_alert.jsonDeterministischer Pfad (ohne MCP / ohne Gateway):
python main.py --alert sample_alert.jsonReine Policy-Prüfung:
python -m gateway.policyRelated MCP server: production-mcp-server
Docker-Deployment
Erfordert Docker + Compose. Secrets bleiben außerhalb des Images:
cp .env.example .env
# set LLM_API_KEY in .envErstellen
docker compose build
# or:
docker build -t secure-agent-mcp-gateway:latest .Drei Dienste (je eine Rolle)
Dasselbe Image; unterschiedliche GATEWAY_ROLE. Jeder Container führt die vollständige Kette
(main → gateway → mcp_server) für diese Rolle aus.
# 1) Viewer
docker compose run --rm triage-viewer
# 2) Operator
docker compose run --rm triage-operator
# 3) Admin
docker compose run --rm triage-adminOder nach Dienstnamen starten:
docker compose up triage-viewer
docker compose up triage-operator
docker compose up triage-adminDen Schlüssel ohne Datei übergeben:
LLM_API_KEY=sk-... docker compose run --rm triage-adminReines Docker (ohne Compose)
docker build -t secure-agent-mcp-gateway:latest .
docker run --rm \
-e LLM_API_KEY \
-e LLM_MODEL=gpt-4o-mini \
-e GATEWAY_ROLE=viewer \
secure-agent-mcp-gateway:latest \
python main.py --mcp --role viewer --alert sample_alert.json
docker run --rm -e LLM_API_KEY -e GATEWAY_ROLE=operator \
secure-agent-mcp-gateway:latest \
python main.py --mcp --role operator --alert sample_alert.json
docker run --rm -e LLM_API_KEY -e GATEWAY_ROLE=admin \
secure-agent-mcp-gateway:latest \
python main.py --mcp --role admin --alert sample_alert.jsonUmgebung
Variable | Zweck |
| Erforderlich für Agent und Findings-Zusammenfassung |
| Standard |
| Standard |
|
|
.env ist gitignoriert. Nur .env.example wird committet.
Rollen (Policy)
Rolle | Kann verwenden |
|
|
| reputation, triage, summarize, notify |
| alle Tools einschließlich |
Definiert in gateway/policy.yaml.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Find, vet, and run MCP tools through a secure audited gateway with prompt-injection risk scoring
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
MCP gateway: one connection for your AI apps, with tool policies, PII redaction and audit logs.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceA secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to safely call enterprise tools through a governed MCP gateway with permission enforcement, blast-radius controls, input validation, and a full audit trail for every invocation.MIT
- AlicenseAqualityCmaintenanceProvides a security governance layer for AI agents to safely access upstream MCP servers, enforcing tool-level RBAC, parameter constraints, authentication via static tokens or OIDC, and tamper-evident audit logging.21Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables governed MCP agent tool invocation with policy-based authorization, short-lived credentials, and audited access control.11 npmMIT