Head to head · Prompt injection detection · October 2026 research run
Azure AI Content Safety (Prompt Shields) vs NVIDIA NeMo Guardrails
NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 3 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on agent ergonomics, security & auth and transparency & trust. Both do prompt injection detection.
Best guardrails and safety filters for AI agents · All 157 guardrails comparisons
Which one, for what
Azure AI Content Safety (Prompt Shields) B
Best for An agent on Azure that retrieves documents and needs indirect-injection checks next to harm-category moderation.
Ahead on
- Agent ergonomics, 78 against 67
- Security & auth, 86 against 62
- Transparency & trust, 83 against 72
Also in its favour
- A hosted endpoint, with nothing to install
Watch for
Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call
Best for Teams that want to compose several checks (their own, NVIDIA's and third-party APIs) behind one OpenAI-compatible endpoint.
Ahead on
- Schema & documentation, 79 against 74
- Payments & pricing, 90 against 23
- Maintenance & community, 70 against 35
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Open source
Watch for
Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Payments & pricing NVIDIA NeMo Guardrails +67
Azure AI Content Safety (Prompt Shields) 23
No x402, MPP or L402 (0). Per-1,000-record prices are public through the Azure Retail Prices API, but the pricing page shows "$-" until a region is chosen in the browser (15 of 20). F0 gives 5,000 free text records and 5,000 images a month, but it needs an Azure subscription and an Azure account needs a card (0). A person signs up and creates the resource in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 15 is 23.
NVIDIA NeMo Guardrails 90
Apache-2.0 package you run yourself with nothing to buy from the project, so 20 for pricing, 20 for a free start and 20 for keyless use. No payment protocol (0). The NemoGuard models it can call are priced separately by NVIDIA. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.
Maintenance & community NVIDIA NeMo Guardrails +35
Azure AI Content Safety (Prompt Shields) 35
Read as a closed service with official SDKs, from Microsoft's dated sources as the other Azure listings are. The newest dated API change is fd7384dc in Azure/azure-rest-api-specs (28 August 2026), which adds Unified Moderate to 2026-09-01-preview, 67 days back (20, was 30, cause time). Later commits touching the folder (17 September SDK generation settings, 29 September folder migration, 14 October linter rulesets) are tooling. The What's New October 2026 section is dated by month only and doesn't set the line. SDK pre-releases on 14 September (Python 1.1.0b1, Java 1.1.0-beta.1) and 18 September (.NET 1.1.0-beta.1, and @azure/ai-content-safety 1.0.0-beta.1, a new JavaScript package) add Prompt Shields, Unified Moderate and provenance calls. Pre-releases off the default install don't count on either line, as the factorial and azure-devops-mcp listings read them, and pip still installs the stable 1.0.0. In the 90 days from 5 August the 28 August spec change counts once. Adding @azure/ai-content-safety at half, whose npm tags we couldn't read, makes 1.5, still under three (0). Microsoft Q&A and a support address answer, and the What's New page was updated in October (5 of 15). The stable SDKs still lag the service, Python 1.0.0 from December 2023 and @azure-rest/ai-content-safety 1.0.1 from January 2025, neither with a Prompt Shields helper (5 of 15). Stable packages unchanged for 35 and 22 months (5 of 10). 20 + 0 + 5 + 5 + 5 = 35.
NVIDIA NeMo Guardrails 70
0.24.1 on 16 September 2026, 46 days before the check, with no release since in the repository's tags (20). Two releases in the 90 days from 3 August, 0.24.0 on 25 August and 0.24.1, with 0.23.0 on 1 July outside (10 of 20, our batch rule for two). 71 commits on develop since 0.24.1, the last on 30 October, are unreleased. Issues get triage labels, but about a dozen opened in August read needs triage, per the 1 October check, not re-read on 1 November (15 of 25). Current package on PyPI, per the 1 October check (15). CI on three operating systems and supported runtimes stated (10). 20+10+15+15+10 = 70.
Security & auth Azure AI Content Safety (Prompt Shields) +24
Azure AI Content Safety (Prompt Shields) 86
Microsoft Entra ID tokens with RBAC, or two resource keys that can be regenerated in turn (30). RBAC can limit a caller, but a resource key also reaches the blocklist write and delete operations, with no confirmation step (15 of 20). Prompt Shields detects user-prompt and document attacks, and the docs describe Spotlighting for third-party content, in preview (15). The Foundry Tools diagnostic logging page describes Audit and RequestResponse logs through Azure Monitor for Cognitive Services resources once the owner adds a diagnostic setting, as the Document Intelligence listing reads it. We didn't confirm the fields for Content Safety (12, was 0). Coordinated disclosure policy and MSRC bounty programmes linked from security.txt, but microsoft.com's security.txt passed its Expires date on 23 September 2026 and still carries it on 3 November (4 of 5), bounty (5), SOC or ISO coverage for Content Safety by name not confirmed (0), MSRC publishes advisories (5), so 14 of 20. An MSRC affected-product search on 3 November finds no CVE naming Content Safety. The 2026 Azure AI Foundry CVEs name Foundry, not this service, so no deduction, as on the Speech, Translator and Document Intelligence listings. 30 + 15 + 15 + 12 + 14 = 86.
NVIDIA NeMo Guardrails 62
Framework reading. No auth of its own, and SECURITY.md says authentication, authorisation, TLS and rate limiting are the deployer's job. Provider keys come from the environment (10 of 30). Tool-input and tool-output rails can block a tool call, but there's no human approval hook, and the LLM-judged tool_safety_check is only on develop since 29 September 2026 (12 of 20). Jailbreak heuristics and model, injection detection and content-safety rails, documented (15). OpenTelemetry tracing to your own backend, opt-in (12 of 15). Disclosure through NVIDIA PSIRT, no bug bounty, no published advisories, and usage telemetry to NVIDIA on by default with a documented opt-out (13 of 20).
Agent ergonomics Azure AI Content Safety (Prompt Shields) +11
Azure AI Content Safety (Prompt Shields) 78
Prompt Shields answers one boolean per prompt and per document, and text analysis returns four or eight severity levels by choice (20 of 25). Categories, output type and haltOnBlocklistHit are set per request (20). Errors carry a code and message in a standard Azure shape, but the codes aren't documented per operation (15 of 20). Checks have no side effects, but there's no retry guidance (15 of 20). Few required fields, but the Python SDK is 1.0.0 from 12 December 2023 with no Prompt Shields method, and the JavaScript package is a generic REST client, 1.0.1 from January 2025 (8 of 15).
NVIDIA NeMo Guardrails 67
Framework reading. An OpenAI client pointed at the server needs no code, but each rail set needs a config directory with config.yml and prompts (20 of 25). /v1/checks returns a RailOutcome of allow, block or transform since 0.24.0 (15 of 20). Streaming rails fail closed when an action errors, but error responses aren't documented as such (12 of 20). Checks are stateless, but every LLM-based rail is an extra model call to budget and retry (12 of 20). Python only, many defaults, and two Colang versions to choose between (8 of 15).
Transparency & trust Azure AI Content Safety (Prompt Shields) +11
Azure AI Content Safety (Prompt Shields) 83
Closed service under Microsoft's product terms (15). The FAQ and the data-privacy page agree that inputs aren't stored, aren't used for training and stay in the resource's region, and that only customer blocklists are kept, encrypted, in that region, per the 1 October check (25 of 30). The overview (updated 28 October) states a deprecation policy, 90 days after a new preview or GA version where compatibility holds, and the What's New page gives dated retirements, the 2025-03-01 retirement announced in October 2024 and six preview capabilities (multimodal analysis, rapid custom categories, both container types, the embedded SDK and groundedness detection) retiring on 30 April 2027 (20, was 15). Processing stays in the resource's region, and regions are listed per feature, but we didn't check a subprocessor list (15 of 20). 15 + 25 + 20 + 15 = 75.
NVIDIA NeMo Guardrails 72
Apache-2.0 with a third-party licence file (30). The telemetry page lists what's sent (version, configuration, which capabilities are switched on, deployment type) and what isn't (prompts, completions, messages, keys, endpoints). We didn't read the code to confirm it (25 of 30). Breaking items are marked per release, but there's no deprecation policy with dates (12 of 20). Telemetry with heartbeats every 10 minutes is on by default, opt-out with NEMO_GUARDRAILS_NO_USAGE_STATS=1, DO_NOT_TRACK=1 or a do_not_track file, and off in CI (15 of 20).
Schema & documentation NVIDIA NeMo Guardrails +5
Azure AI Content Safety (Prompt Shields) 74
Public OpenAPI (Swagger) documents in Azure/azure-rest-api-specs, with stable 2024-09-01 and previews up to 2026-09-01-preview, error schemas and examples on all 15 operations (25). learn.microsoft.com has no llms.txt (404 on 3 November), but its pages answer Accept: text/markdown with Markdown, as the Document Intelligence, Key Vault and Foundry fine-tuning listings read it (5, was 0). The concept pages explain each check and list use cases, but don't say when not to use one (12 of 20). Prompt Shields takes userPrompt and up to five documents as plain strings, with "at least one" stated in prose rather than the schema, while text analysis has category and output-type enums (12 of 15). Request and response examples on the REST reference, a typed ErrorResponse with code, message and x-ms-error-code, but no list of error codes (12 of 15). api-version on every call and a What's New page, whose newest section (October 2026, a model update and dated retirements) still doesn't mention the 2026-07-01-preview and 2026-09-01-preview versions in the spec repository (8 of 15). 25 + 5 + 12 + 12 + 12 + 8 = 74.
NVIDIA NeMo Guardrails 79
Framework reading. Rail configuration is typed in Python and validated on load, and the server speaks the OpenAI chat-completions shape. The repository holds a Fern OpenAPI file, generated at docs build time since 23 October 2026, but no published OpenAPI document for /v1/checks was found in the docs (15 of 25). The docs serve llms.txt at docs.nvidia.com/nemo/guardrails/llms.txt, with a 681-line index of Markdown pages for the latest version and one per release from 0.22.0 (10). The docs describe each rail type and the built-in and third-party rails, and 0.24.0 added IORails, which runs input and output rails without the Colang runtime (15 of 20). YAML configuration with typed models, though Colang 1 and Colang 2 coexist (12 of 15). An examples tree in the repository and per-rail guides, little on error responses (12 of 15). Semver releases and a dated changelog (15). 15+10+15+12+12+15 = 79.
Score by category
| Category | Weight | Azure AI Content Safety (Prompt Shields) | NVIDIA NeMo Guardrails | Edge |
|---|---|---|---|---|
| Reliability | 16% | 75 | 75 | even |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 79 | NVIDIA NeMo Guardrails +5 |
| Agent ergonomics | 13% | 78 | 67 | Azure AI Content Safety (Prompt Shields) +11 |
| Security & auth | 14% | 86 | 62 | Azure AI Content Safety (Prompt Shields) +24 |
| Payments & pricing | 10% | 23 | 90 | NVIDIA NeMo Guardrails +67 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 70 | NVIDIA NeMo Guardrails +35 |
| Transparency & trust | 7% | 83 | 72 | Azure AI Content Safety (Prompt Shields) +11 |
| Negative events | ≤15 | 0 | 0 | |
| Total | B 68/100 | BB 73.2/100 |
Facts side by side
| Fact | Azure AI Content Safety (Prompt Shields) | NVIDIA NeMo Guardrails |
|---|---|---|
| Kind | HTTP API | Agent framework |
| Vendor | Microsoft | NVIDIA |
| Hosted endpoint | https://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompt | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | None |
| Pricing | Freemium | Free |
| x402 | no | no |
| Licence | none | Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-08-28 | 2026-09-16 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | 2026-09-01 | no date given |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Popularity | 17k npm/wk, 218k PyPI/wk | 7.2k stars, 101k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Azure AI Content Safety (Prompt Shields) | NVIDIA NeMo Guardrails |
|---|---|---|
| QuillDocumentation and schema critic | 3/5 A good OpenAPI file, and an SDK that can't call Prompt Shields | 3/5 Typed rail config, but no contract for /v1/checks |
| WardenSecurity auditor | 3/5 The resource key can delete the blocklists it enforces | 3/5 No auth by design, and a heartbeat to NVIDIA every 10 minutes |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Azure AI Content Safety (Prompt Shields)
Prompt Shields checks up to five retrieved documents for indirect injection, not only the user prompt, and the API has its own 99.9 per cent SLA level. Needs an Azure subscription with a card, a resource and a region that has the feature, and the stable SDKs date from 2023 and January 2025.
NVIDIA NeMo Guardrails
Apache-2.0, 7,200 stars and nine releases between 9 October 2025 and 16 September 2026. Usage telemetry and a heartbeat every 10 minutes to NVIDIA by default.
Before you call either
Azure AI Content Safety (Prompt Shields)
- Send retrieved pages and tool results in the documents array of shieldPrompt, not in userPrompt, so document attacks are reported separately
- Call text:shieldPrompt over REST with api-version=2024-09-01. The stable Python SDK 1.0.0 has no method for it, only the 1.1.0b1 pre-release
- Keep each request under 10,000 characters across prompt and documents, and split long tool results
- Create the resource in a region that lists Prompt Shields, since not every region has it
- On F0 you get 5 requests a second. Queue checks or move to S0 before load testing
- Don't build on groundedness detection, multimodal analysis or rapid custom categories. They retire on 30 April 2027
NVIDIA NeMo Guardrails
- Set NEMO_GUARDRAILS_NO_USAGE_STATS=1 before import unless you want deployment metadata sent to NVIDIA every 10 minutes
- Use IORails for plain input and output checks. LLMRails and Colang are for dialogue flows a tool-calling agent rarely needs
- Pin nemoguardrails==0.24.1. 0.24.0 changed message passing to messages= and removed inline config from /v1/checks
- Call /v1/checks with a config_id loaded on the server and branch on the RailOutcome
- Put the server behind your own gateway. It has no auth or rate limiting
Questions
Which is better for AI agents, Azure AI Content Safety (Prompt Shields) or NVIDIA NeMo Guardrails?
NVIDIA NeMo Guardrails scores 73.2 (BB) on agent readiness against Azure AI Content Safety (Prompt Shields)'s 68 (B), and leads in 3 of 7 scored categories. Azure AI Content Safety (Prompt Shields) leads on agent ergonomics, security & auth and transparency & trust.
Can an agent call Azure AI Content Safety (Prompt Shields) and NVIDIA NeMo Guardrails without installing anything?
Azure AI Content Safety (Prompt Shields) has a hosted endpoint at https://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPrompt. No hosted endpoint is listed for NVIDIA NeMo Guardrails.
Are Azure AI Content Safety (Prompt Shields) and NVIDIA NeMo Guardrails open source?
No open-source release is listed for Azure AI Content Safety (Prompt Shields). NVIDIA NeMo Guardrails is open source (Apache-2.0).
Other comparisons with Azure AI Content Safety (Prompt Shields) or NVIDIA NeMo Guardrails
- Azure AI Content Safety (Prompt Shields) vs Llama Guard 4
- Azure AI Content Safety (Prompt Shields) vs Mistral Moderation API
- Azure AI Content Safety (Prompt Shields) vs OpenAI Moderation API
- Azure AI Content Safety (Prompt Shields) vs ShieldGemma
- Granite Guardian vs NVIDIA NeMo Guardrails
- Llama Guard 4 vs NVIDIA NeMo Guardrails
- Mistral Moderation API vs NVIDIA NeMo Guardrails
- NVIDIA NeMo Guardrails vs OpenAI Moderation API
- NVIDIA NeMo Guardrails vs ShieldGemma
- Amazon Bedrock Guardrails vs Azure AI Content Safety (Prompt Shields)
- Amazon Bedrock Guardrails vs NVIDIA NeMo Guardrails
- Azure AI Content Safety (Prompt Shields) vs Cisco AI Defense Inspection API
- Azure AI Content Safety (Prompt Shields) vs Google Cloud Model Armor
- Azure AI Content Safety (Prompt Shields) vs Granite Guardian
- Azure AI Content Safety (Prompt Shields) vs Guardrails AI
- Azure AI Content Safety (Prompt Shields) vs Lakera Guard (Check Point AI Guardrails)
- Azure AI Content Safety (Prompt Shields) vs LlamaFirewall
- Azure AI Content Safety (Prompt Shields) vs OpenAI Guardrails
- Azure AI Content Safety (Prompt Shields) vs Prisma AIRS AI Runtime Security API
- Cisco AI Defense Inspection API vs NVIDIA NeMo Guardrails
- Google Cloud Model Armor vs NVIDIA NeMo Guardrails
- Guardrails AI vs NVIDIA NeMo Guardrails
- Lakera Guard (Check Point AI Guardrails) vs NVIDIA NeMo Guardrails
- LlamaFirewall vs NVIDIA NeMo Guardrails
- NVIDIA NeMo Guardrails vs OpenAI Guardrails
- NVIDIA NeMo Guardrails vs Prisma AIRS AI Runtime Security API
- AgentGate vs Azure AI Content Safety (Prompt Shields)
- AgentGate vs NVIDIA NeMo Guardrails
- Presidio vs NVIDIA NeMo Guardrails
Machine-readable
- This page as Markdown
/compare/azure-ai-content-safety-vs-nemo-guardrails.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-ai-content-safety.json·/api/v1/tools/nemo-guardrails.json - From a terminal
anchor compare azure-ai-content-safety nemo-guardrails(the CLI) - Over MCP
compare_tools {"a": "azure-ai-content-safety", "b": "nemo-guardrails"}at/mcp, no key