Don’t attach the Injection Protection Policy to an AI Consumer or an AI Consumer Group. Doing so stops the data plane from applying configuration changes. The data plane keeps running its previous configuration until you detach the policy.
Requests that carry SQL, script, or other injection payloads in a path, query string, header, or body can reach your models and tools unchecked. The Injection Protection AI Policy compares each request against regular expressions for known injection patterns, and either rejects matching requests or logs them. This policy can complement your existing firewall solution by adding a layer of customizable protection to prevent injection attacks, or it can eliminate some content-based attacks if you don’t have an existing firewall. Attach the policy to your AI Models, AI Agents, or AI MCP Servers, or apply it globally.