Runtime authorization & controls
Gateway layer from Kong that proxies LLM provider traffic and remote MCP traffic, exposes existing APIs as MCP tools, and applies authentication, access control and rate limiting plugins to those calls. Documentation emphasises traffic governance; semantic guardrails and agent threat detection are not covered on the fetched pages.
hybrid · generally available · Research snapshot 2026-09-06
Visit the official product source ↗Runtime authorization & controls · Observability & traceability
Useful conversation with: API platform owner, Platform engineering lead, Enterprise architect.
Show me an internal REST API exposed as an MCP tool through Kong, protected by the AI MCP OAuth2 plugin, with a rate limit and traffic log for each tool call.
Support labels reflect the supplied research. Documentation and vendor claims are not independent product tests. “Not established” means the researcher did not find support; it does not prove a capability is absent.
Documented by provider
Kong AI Gateway acts as a trust and control layer for proxying traffic to MCP servers, enforcing access controls for MCP tool usage and securing MCP endpoints with the AI MCP OAuth2 plugin.
Limit: The page does not document authorization policy syntax, per-tool consent, or human approval steps.
Documented by provider
The AI MCP Proxy plugin converts API schemas into MCP tool definitions and aggregates multiple APIs into a single MCP server endpoint without requiring an LLM.
Limit: Conversion behaviour for complex or streaming APIs is not detailed.
Documented by provider
AI Gateway policies can inspect request bodies so the gateway can act on the prompts passing through it, alongside routing, failover and load balancing across LLM providers.
Limit: Prompt inspection is described generically; no prompt-injection detector or safety classifier is documented on this page.
Listing does not imply partnership, supplier status, a working DutyGraph integration, or a compliance certification.
Suggest a correction