The Model Context Protocol (MCP) gateway is now generally available (GA) as part of the Red Hat Connectivity Link 1. 5 release, and natively integrated into the Red Hat AI portfolio. This follows a successful technology preview , and expands Red Hat's enterprise AgentOps capabilities to govern AI agent tool traffic at scale. We've added new features, including gateway isolation, stateless session support, prompts and resources support, MCP guardrails, and security hardening to make it ready for production use. You can cater to different teams and tenants in your organization by isolating MCP agent traffic.
There are 2 ways to do this. The first is to delegate a completely separate gateway instance, including the MCP gateway components (the router and broker). This approach keeps the traffic isolated from each other all the way through to the back-end MCP server. The second way is to use a shared gateway, providing isolation from the gateway listener level down. Separate MCP gateway components are still used, which keeps the traffic isolated after the gateway routing logic is triggered.
This allows the core gateway infrastructure to be shared with different endpoints for sets of MCP servers behind a single gateway endpoint (for example, /mcp-team-a and /mcp-team-b ). The gateway now federates MCP prompts from upstream servers alongside tool-calling capabilities. Prompts are prefixed the same way as tools and are accessible through prompts/list and prompts/get through the gateway. Authorization filtering supports prompts using the allowed-capabilities JWT claim. A virtual server can scope prompts with the spec.
prompts field on the MCPVirtualServer resource, verifying that AI agents are constrained to authorized system prompts and context. Resource federation currently covers the resources/list and resources/read methods for prefixed ui:// resources, primarily on the stateful path. Like tools and prompts, you can filter resources based on authorization rules to govern the enterprise data surfaced to agents. As the number of tools behind a gateway grows across enterprise MCP catalogs, returning everything in a single tools/list response becomes impractical and degrades LLM context efficiency.