Topic starter
24/06/2026 8:05 pm
TL;DR: Inline inspection, prompt-injection blocking, and data-loss controls are now being applied at the API gateway layer for AI and MCP traffic, according to Kong. The governance question is no longer whether AI needs protection, but which identity and policy controls can operate fast enough to keep model inputs, outputs, and tool calls within acceptable bounds.
Editorial analysis by NHI Mgmt Group, based on content published by Kong: “# Secure AI at Scale: Prisma AIRS and Kong AI Gateway Now Integrated”.
Key questions
Q: How should security teams handle prompt injection in AI systems?
A: Treat prompt injection as an authorisation problem, not only a content problem.
Q: Why do MCP tools need explicit authorisation controls?
A: Because MCP turns tools into callable capabilities, and capability exposure is a privilege problem, not just an integration pattern.
Q: What breaks when AI security only inspects user inputs?
A: The response path remains uncontrolled, which means unsafe output, malicious code, or sensitive data can leave the trust boundary even when the inbound prompt looked safe.
Practitioner guidance
- Define the gateway as an AI policy boundary Map prompt inspection, response inspection, and tool-call control to one enforcement point so security decisions happen before model execution and before downstream exposure.
- Classify MCP tools as governed capabilities Inventory which tools an agent or model can reach through MCP and require explicit authorisation rules for each capability, not a blanket assumption of access.
- Add bidirectional content controls Block or redact sensitive data and unsafe outputs on both ingress and egress so the response path cannot become an unmonitored leak channel.
Bottom line: AI gateway enforcement is shifting AI security from application-specific checks to a central control point for prompts, responses, and tool calls.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 5:15 am
Edge enforcement is becoming the new AI governance boundary: once prompts, responses, and tool calls all flow through a gateway, policy has to operate where traffic is still inspectable. That shifts AI security away from application-by-application controls and toward centralised runtime governance. The practical consequence is that identity and data protections become part of the same enforcement plane for AI systems.
A question worth separating out:
Q: How should teams decide whether to secure AI traffic in the gateway or in each application?
A: Use the gateway when multiple applications, models, or tools share the same AI traffic patterns and policy decisions need to stay consistent. Use per-application controls only for narrowly scoped exceptions. A central gateway is the better fit when identity, safety, and audit requirements must apply everywhere.
👉 Read our full editorial: Kong AI Gateway integration shifts AI traffic security to the edge