01 — Inventory
Register each approved upstream endpoint under one customer tenant. A credential for one tenant cannot reach another tenant’s server.
Maha StrategiesEnterprise infrastructure
One governed path to your MCP servers.
The Enterprise MCP Gateway is the shared control layer for a tenant’s approved MCP connections: server inventory, explicit method and tool allowlists, tenant-bound credentials, and an audit record that does not retain request contents.
Three controls
Inventory, policy, evidence.
02 — Policy
Allow only the MCP methods and tool names you have explicitly registered. Unlisted calls are blocked before any upstream request is made.
03 — Evidence
Record the method, tool name, outcome, upstream status, and a request hash—not the request body, tool arguments, or upstream response.
Known limits
Current deployment boundary
The canonical v1 gateway proxies JSON MCP messages to registered public HTTPS upstreams. Bearer and HMAC upstream credentials are encrypted at rest and never returned. The gateway does not yet provide private-network connectivity, upstream OAuth token exchange, SSE streaming, or browser-originated calls.
Allowlist
Supported policy surface
initializepingtools/listresources/listresources/readprompts/listprompts/gettools/calltools/call requires a named per-server allowlist. A registered server URL is not permission to invoke every tool it exposes.
Containment
Discovery and failure containment
Registration performs a bounded tools/list handshake. Operators approve callable tools from that validated inventory, then set tenant-wide request rate, timeout, failure-threshold, and circuit-cooldown controls.
Discovery describes the upstream surface; it does not authorize a tool automatically.
Machine-readable
Contract and architecture guides
Integration teams can use the gateway contract to register a server and make requests through a tenant endpoint, then review the exact control boundary before routing production tools.