Guardrails
Guardrail layers at the gateway: input masking on every request, response masking optional; prompt injection and hallucination protection coming soon.
Every request that passes through the Gateway goes through guardrail layers before it leaves for the external model. The layers running today are based on masking; two more will be added at the same checkpoint.
| Layer | What it does | Status |
|---|---|---|
| Input masking | Masks personal data inside the request before the model sees it | On (default) |
| Response masking | Masks personal data returned by the model before it reaches the client | Optional |
| Prompt injection protection | Flags inputs that aim to push the model outside the instructions it was given | Coming soon |
| Hallucination protection | Flags model responses that have no grounding | Coming soon |
Input masking
This is the default layer, and it runs on every request. Text is scanned
before it is forwarded to the external model, each detected piece of personal
data is replaced with a placeholder such as <PERSON_1>, and only masked text
goes to the model.
Coverage is 26 categories; the special categories of personal data under Article 6 of KVKK are included. For the full list and synthetic examples see Categories, and for the placeholder format see Concepts.
If masking cannot be completed, the request does not go to the external model and the Gateway returns a 502. There is no “send it unmasked anyway” option.
Response masking
Input is masked on every request; the response side is enabled when the organization requests it. If the model produces personal data in its response or repeats a value from the input, those values are masked before they return to the client.
It is not applied to streaming responses: to avoid breaking the real-time stream, the response passes through as-is, and this is recorded in the audit trail.
Turning masking off
Masking can be turned off per virtual key; requests from that key go directly to the language model, and for that key the Gateway acts as a plain AI gateway. Masked and unmasked keys can run side by side in the same organization.
Layers coming soon
Two layers are in development. Both are designed to run at the same checkpoint, in the same flow as masking.
Prompt injection protection. Flags attempts hidden in user input that aim to push the model outside the instructions it was given. A typical example is an instruction of the “ignore the previous instructions” kind placed inside otherwise ordinary text.
Hallucination protection. Flags cases where the model gives an answer with no grounding in a confident tone. This is a different risk from a personal data leak: here the problem is not data going out, but wrong information coming in.
When they go live, this page will be updated and a dated entry will be added to the Release notes page.