Agent Gateway

In this catalog it is the Agentic Gateways option when you need to front agents and MCP/tool surfaces safely. Keep Agent Gateway on the observe/propose side of the loop: useful signals and drafts, with human or policy authority still required before anything irreversible runs.

Clients connect to the gateway/registry; it authenticates, discovers MCP/agent servers, and proxies tool or agent traffic under configured policy.

1. Register or discover the MCP/agent servers the gateway will front.
2. Configure authn/z and allow-lists for tools.
3. Proxy a tool call from a test agent and verify policy denials.
4. Cut agent runtimes over to the gateway endpoint.

Related: model-context-protocol · mcp-gateway-registry · topics/12-central-nervous-system · topics/33-skill-registry

• Use when: Agent Gateway is an open gateway aimed at agent traffic patterns — mediating how agents reach tools/services with agent-aware controls matches the bottleneck and you specifically need to front agents and MCP/tool surfaces safely.
• Skip when: another pack already covers the need with less ops surface, or Agent Gateway would become a second place people retype truth.
• Prefer instead: compare Model Context Protocol, MCP Gateway Registry before locking the cell.

• Ops: confirm license, hosting, and release cadence for Agent Gateway (agentgateway/agentgateway) before relying on it in a live corridor.
• Integration: bad credentials, scopes, or schema drift produce empty retrievals or runaway tool/model spend without an obvious UI alarm.
• Scope: Agentic Gateways components support agents; they are not the company ledger or the approval authority.