Once more than one team is building agents, a question arrives that nobody owns: which MCP servers exist, who is allowed to call which tool, and where is the record of what happened? Individual MCP servers can be built well and the estate can still be ungoverned.
Status: product concept, in active development. This is something we are building, not something you can buy today. We publish our roadmap because the engineering thinking behind it is the useful part — and because we would rather show you the design than imply a finished product.
The Enterprise MCP Gateway and Registry is designed as the control plane for that estate — every AI client reaching business systems through one enforced, observable path.
Designed Capabilities
- Server onboarding and discovery catalog — a single answer to what MCP servers exist and what they expose.
- User, agent and workload identity — agents get identities, not shared credentials.
- Tool-level authorization policies — permission granted per tool, not per server.
- Schema and argument validation — arguments are validated at the boundary, because a model can be manipulated into sending hostile values.
- Secret isolation and connection brokering — the agent never holds the credential.
- Rate limits and session controls — a runaway agent cannot exhaust a downstream system.
- Human approval for sensitive tools — the consequential path is gated by design.
- Health, usage and immutable audit reporting — reconstruct what any agent did, and prove it.
The Argument For a Gateway
An MCP server is a security boundary. A fleet of them, each configured by whoever built it, is a boundary with unknown gaps. Centralising identity, policy and audit is the difference between “we think our agents are constrained” and being able to demonstrate it.
This extends our MCP development practice from building good individual servers to governing many. Where an independent assessment of that boundary is wanted, our sister practice covers AI and MCP security.
Tell us if this matches a problem you have — early input shapes what we build first, and we will give you an honest view of where it stands.