AI Semantic Response Guard

AI License Required
Related Documentation
Made by
Kong Inc.
Supported Gateway Topologies
hybrid db-less traditional
Supported Konnect Deployments
hybrid cloud-gateways serverless
Compatible Protocols
grpc grpcs http https
Minimum Version
Kong Gateway - 3.12
Tags
#ai
AI Gateway Enterprise: This plugin is only available as part of our AI Gateway Enterprise offering.

The AI Semantic Response Guard plugin extends the AI Prompt Guard plugin by filtering LLM responses based on semantic similarity to predefined rules. It helps prevent unwanted or unsafe responses when serving llm/v1/chat, llm/v1/completions, or llm/v1/embeddings requests through Kong AI Gateway.

You can use a combination of allow and deny response rules to maintain integrity and compliance when returning responses from an LLM service.

How it works

The plugin analyzes the semantic content of the full LLM response before it is returned to the client. The matching behavior is as follows:

  • If any deny_responses are set and the response matches a pattern in the deny list, the response is blocked with a 400 Bad Request.
  • If any allow_responses are set, but the response matches none of the allowed patterns, the response is also blocked with a 400 Bad Request.
  • If any allow_responses are set and the response matches one of the allowed patterns, the response is permitted.
  • If both deny_responses and allow_responses are set, the deny condition takes precedence. A response that matches a deny pattern will be blocked, even if it also matches an allow pattern. If the response does not match any deny pattern, it must still match an allow pattern to be permitted.

Response processing

To enforce these rules, the plugin:

  1. Disables streaming (stream=false) to ensure the full response body is buffered before analysis.
  2. Intercepts the response body using the guard-response filter.
  3. Extracts response text, supporting JSON parsing of multiple LLM formats and gzipped content.
  4. Generates embeddings for the extracted text.
  5. Searches the vector database (Redis, Pgvector, or other) against configured allow_responses or deny_responses.
  6. Applies the decision rules described above.

If a response is blocked or if a system error occurs during evaluation, the plugin returns a 400 Bad Request to the client without exposing that the Semantic Response Guard blocked it.

Something wrong?

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!