Skip to main content
Glama
aki83reo

Secure Agent MCP Gateway

by aki83reo

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.json

Deterministischer Pfad (ohne MCP / ohne Gateway):

python main.py --alert sample_alert.json

Reine Policy-Prüfung:

python -m gateway.policy

Related MCP server: Nervora

Docker-Deployment

Erfordert Docker + Compose. Secrets bleiben außerhalb des Images:

cp .env.example .env
# set LLM_API_KEY in .env

Erstellen

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 (maingatewaymcp_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-admin

Oder nach Dienstnamen starten:

docker compose up triage-viewer
docker compose up triage-operator
docker compose up triage-admin

Den Schlüssel ohne Datei übergeben:

LLM_API_KEY=sk-... docker compose run --rm triage-admin

Reines 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.json

Umgebung

Variable

Zweck

LLM_API_KEY

Erforderlich für Agent und Findings-Zusammenfassung

LLM_MODEL

Standard gpt-4o-mini

LLM_PROVIDER

Standard openai

GATEWAY_ROLE

viewer | operator | admin

.env ist gitignoriert. Nur .env.example wird committet.

Rollen (Policy)

Rolle

Kann verwenden

viewer

check_ip_reputation

operator

reputation, triage, summarize, notify

admin

alle Tools einschließlich block_ip + escalate_alert

Definiert in gateway/policy.yaml.

F
license - not found
Not graded
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A 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
  • A
    license
    Not graded
    quality
    A
    maintenance
    A zero-trust security gateway for MCP tool calls, inspecting tool identity, arguments, execution decisions, and returned content before risk reaches your coding agent.
    Apache 2.0
  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables AI agents to securely call MCP tools with risk scoring, checkpoints, rollback, and approval workflows.
    134
    MIT

View all related MCP servers

Related MCP Connectors

  • Runtime permission, approval, and audit layer for AI agent tool execution.

  • Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.

  • Remote MCP for A2A caller identity, scope policy, verdict receipts, and audit history.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aki83reo/secure-agent-mcp-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server