A governed registry
Register MCP servers, review their configuration and manage approval before making them available through the gateway.
MCP Gateway
Give agents access to approved MCP servers through a gateway that understands identity, JSON-RPC methods, scanning and request evidence.
Tools are an access boundary
Register MCP servers, review their configuration and manage approval before making them available through the gateway.
Apply identity-aware access policies, JSON-RPC method controls and rate limits before a call reaches the upstream MCP server.
Scan request and response content, add optional ICAP DLP and review gateway decisions in MCP request logs.
From registration to runtime
Bring external and hosted servers into the MCP registry. Source and runtime scanning help reviewers understand findings before approval; scanning does not guarantee a server is safe.
Review the server and its access configuration before exposing a governed endpoint to clients and agents.
Use supported hosted-MCP deployment and supervision paths to manage lifecycle and runtime health.
Apply the configured firewall, content-scanning and DLP policies to JSON-RPC traffic. Record allowed and blocked request decisions for investigation.
A concrete control
An agent attempts a JSON-RPC method outside the configured allowlist. AI Warden denies the request before forwarding it to the registered server.
Reviewers can investigate the caller, target, matched policy and decision in the request log.
Illustrative enforcement event
Questions, answered
AI Warden supports registration of external MCP servers alongside supported hosted servers. Confirm transport, authentication and deployment compatibility during a technical review.
Yes. Optional ICAP checks can inspect MCP JSON-RPC requests and responses. SSE response inspection works on complete events so partial content is not delivered before that event is approved.
See AI Warden in action
Bring your models, tools and security requirements. See how AI Warden puts them under one control plane.