AI Policies

Create an AI Policy when you want to add governance, security, transformation, or observability to AI Gateway traffic. For example:

• Redact sensitive data with AI PII Sanitizer
• Manage request volume with AI Rate Limiting Advanced
• Validate prompts with AI Prompt Guard or other guardrail Policies
• Track requests and responses for observability with logging Policies

To control access and verify identity, assign an AI Auth Strategy instead of an AI Policy.

Each AI Policy is independent. To apply the same configuration across multiple entities, create separate Policies for each one. This ensures that deleting an entity deletes only its own Policies, not configurations shared with other parts of your gateway.

For the complete set of available policy types and configurations, see the AI Policies hub.

AI Policies are managed through:

• Konnect UI
• AI Gateway API: /v1/ai-gateways/{aiGatewayId}/policies
• kongctl

For configuration examples and step-by-step setup instructions, see Set up a global AI Policy.

An AI Policy’s scope is determined by where it’s referenced. Each AI Policy is an independent configuration that applies at exactly one scope. To apply identical configuration in multiple places, create one AI Policy per target.

The available scopes are:

• Global: An AI Policy with no parent entity reference applies to all AI Gateway traffic on the data plane. Non-AI traffic on the same data plane isn’t affected.

• Entity-scoped: Reference the policy from the policies array on an AI Model, AI Agent, AI MCP Server, AI Consumer, or AI Consumer Group entity. The policy applies at that entity’s scope.

An AI Policy specifies a type (like AI Sanitizer or AI Rate Limiting Advanced) and a config block that configures that behavior. AI Gateway applies the policy at the scope you choose: globally across all traffic, or scoped to a specific entity.

The following example creates a global AI PII Sanitizer Policy that runs for every AI Gateway Route. It anonymizes high-risk PII categories (email, phone, SSN, and credit cards) along with custom patterns for sensitive tokens like AWS API keys and GitHub tokens.

This Policy connects to an AI PII Anonymizer service at host/port (sanitizer-service.internal:8080 in this example) to perform the actual sanitization. Substitute the address of your own running instance. See AI PII Anonymizer service for image access and setup instructions.

Without a reachable service at that address, requests through this Policy will fail.

curl -X POST https://{region}.api.konghq.com/v1/ai-gateways/{AIGatewayId}/policies \
    --header "accept: application/json" \
    --header "Content-Type: application/json" \
    --header "Authorization: Bearer $KONNECT_TOKEN" \
    --data '
    {
      "display_name": "PII Sanitizer - Global",
      "name": "pii-sanitizer-global",
      "type": "ai-sanitizer",
      "enabled": true,
      "global": true,
      "config": {
        "anonymize": [
          "email",
          "phone",
          "ssn",
          "creditcard",
          "custom"
        ],
        "custom_patterns": [
          {
            "name": "aws_api_key",
            "regex": "AKIA[0-9A-Z]{16}",
            "score": 0.95
          },
          {
            "name": "github_token",
            "regex": "ghp_[A-Za-z0-9]{36}",
            "score": 0.9
          }
        ],
        "host": "sanitizer-service.internal",
        "port": 8080,
        "redact_type": "placeholder",
        "stop_on_error": true,
        "recover_redacted": false
      }
    }
    '

ai_gateway_policies:
  - ref: pii-sanitizer-global
    ai_gateway: !lookup {id: !env AI_GATEWAY_ID}
    display_name: PII Sanitizer - Global
    name: pii-sanitizer-global
    type: ai-sanitizer
    enabled: true
    global: true
    config:
      anonymize:
      - email
      - phone
      - ssn
      - creditcard
      - custom
      custom_patterns:
      - name: aws_api_key
        regex: AKIA[0-9A-Z]{16}
        score: 0.95
      - name: github_token
        regex: ghp_[A-Za-z0-9]{36}
        score: 0.9
      host: sanitizer-service.internal
      port: 8080
      redact_type: placeholder
      stop_on_error: true
      recover_redacted: false