Niches · Guardrails & safety filters
Enforce one guardrail policy on every request through a gateway
No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.
What counts as done
Every request route the gateway serves (chat, Responses, Messages, batch, streaming) is screened, the whole conversation is checked rather than only the last message, a check that did not run is logged as not run, and a block returns a reason the caller can act on.
Measured, for our own tests: the check adds under 150 ms at the median for a 2,000-token request. No docs we read state these figures, so they don't count against a listing here.
How agents ask for it: put a guardrail in front of all our model traffic
, make every team's calls go through the same checks
, add Bedrock or Model Armor screening to our LiteLLM proxy
Does the job, with a limit 9
It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.
| Listing | Why |
|---|---|
| Amazon Bedrock Guardrails A Amazon Web Services, Inc. | ApplyGuardrail screens text and image content blocks with per-policy assessments and errors as HTTP codes, but tool-use fields are skipped (acc-18) and a gateway integration dropped images from the payload (acc-19). source |
| Azure AI Content Safety (Prompt Shields) B Microsoft Corporation | shieldPrompt takes one userPrompt and up to five documents, not a message history, within 10K characters; no fail-mode or not-run status is documented, and document attack detection is off by default in Foundry. source |
| Cisco AI Defense Inspection API B Cisco Systems, Inc. | Chat inspection takes the whole messages array, HTTP inspection covers raw requests, and the SDK has a gateway mode with enforce or monitor; but the API never blocks itself and no fail-mode or not-run status was found in what was read. source |
| Google Cloud Model Armor BB Google LLC | Each prompt or response is inspected as a single-turn request with no conversation history; a skipped or failed check is reported (EXECUTION_SKIPPED, invocation_result FAILURE), but acc-20 and acc-21 show Responses traffic unscreened and batches failing in a gateway. source |
| Lakera Guard (Check Point AI Guardrails) B Check Point Software Technologies Ltd. | Only the last interaction is screened, earlier turns are context; content type text only, so images are not checked. acc-22 saw a 403 with no detector named and acc-24 a v1 body sent to v2 that blocked all traffic. source |
| Mistral Moderation API B Mistral AI (RCS Paris 952 418 325) | Inline guardrails with per-category thresholds, action block and block_on_error cover Mistral's chat, conversations and agents only; the conversational endpoint classifies the last turn, and text only. source |
| NVIDIA NeMo Guardrails BB NVIDIA Corporation | The server fronts any model with an OpenAI-compatible endpoint and /v1/checks, and tool rails fail closed, but acc-03 found only the last user message checked and acc-04 that a cut-off verdict passes as safe. source |
| OpenAI Guardrails BB OpenAI (as named in the LICENSE copyright line and the PyPI author field) | A client wrapper rather than a gateway; checks fail open unless raise_guardrail_errors=True, and the prompt injection check's own table gives a 1,481 ms median for the default model, far above the 150 ms bar. source |
| Prisma AIRS AI Runtime Security API C Palo Alto Networks, Inc. | Every response carries action allow or block, a category, and errors for detection services that failed or timed out; but only the last element of contents is scanned, earlier turns are context, and content is text only. source |
Couldn't check 1
The docs were closed to us, or silent. These carry no mark either way.
| Listing | Why |
|---|---|
| Guardrails AI D Guardrails AI, Inc. | The docs site returned 404, and the repository pages read do not say which request routes the API server screens, whether history is checked, or how a validator that fails to run is reported. |
Doesn't do this job 7
Listings in the category that do something else, with the reason.
| Listing | Why |
|---|---|
| AgentGate D Mohit Singh (individual) | Sits between an agent and its tools, assessing tool invocations; it does not screen chat, Responses, Messages or batch model traffic. source |
| Granite Guardian B International Business Machines Corporation | An 8B judge model the owner runs, one criterion per call; not a gateway or policy layer. source |
| Llama Guard 4 D Meta Platforms, Inc. | A classifier model the owner hosts, not a policy layer; no injection or PII checks, and the card sends readers to Prompt Guard 2 for prompt attacks. source |
| LlamaFirewall D Meta Platforms, Inc. | An in-process Python library that scans messages the agent hands it; it is not a proxy and has no route coverage, moderation or PII masking. source |
| Presidio B Data Privacy Stack (community organisation, no legal entity stated) | A PII detection and anonymisation library with no gateway, injection or moderation checks of its own; route coverage belongs to the proxy that calls it, and acc-15, acc-16 and acc-43 show LiteLLM's Presidio path missing tool arguments and streams. source |
| OpenAI Moderation API BB OpenAI OpCo, LLC | A harm classifier, not a policy layer: no injection, PII or conversation-wide checks, and inline moderation on a streamed generation arrives only after the full output. source |
| ShieldGemma C Google LLC (RDAP registrant of gemma.ai; the Gemma Terms of Use are Google's and the cards name Google as author) | An open-weight classifier the owner runs, one policy per call; no injection or PII checks and no gateway. source |
What stops agents finishing
- guardrail reads only chat-completions messages, so Responses or batch traffic passes unscreened
- API version change makes every check fail and the gateway blocks all traffic
- image parts dropped from the guardrail payload while still sent to the model
Around it
Before: inference.failover-routing. After: agent-observability.gateway-logging, human-in-the-loop.audit-decisions.
Where this comes from
Weight 19 of 100 in Guardrails & safety filters: 11 of 50 accounts: LiteLLM, Otari, Future AGI and OpenClaw-plugin issues where guardrails skipped a route, dropped images, failed open or blocked everything, plus a NeMo gateway integrator's latency benchmark
The same as data: /api/v1/use-cases/guardrails.gateway-enforcement.json, or the MCP tool get_use_case with id guardrails.gateway-enforcement. Other jobs in this category: /api/v1/niches?category=guardrails.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.