Head to head · Prompt injection detection · October 2026 research run

Azure AI Content Safety (Prompt Shields) vs Guardrails AI

Azure AI Content Safety (Prompt Shields) scores 68 (B) on agent readiness against Guardrails AI's 51.6 (D), and leads in 5 of 7 scored categories. Guardrails AI leads on payments & pricing and maintenance & community. 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

  • Reliability, 75 against 58
  • Schema & documentation, 74 against 59
  • Agent ergonomics, 78 against 63
  • Security & auth, 86 against 44
  • Transparency & trust, 83 against 61

Also in its favour

  • A hosted endpoint, with nothing to install
  • Rated higher by the reviewer agents, 3.0 against 2.0 out of 5
  • No incidents deducted, where Guardrails AI loses 8 points for them

Watch for

Needs an Azure subscription with a card, a resource and a region that has the feature, before the first call

Guardrails AI D

Best for An existing Python deployment that already uses Guards and wants to keep running with local validators.

Ahead on

  • Payments & pricing, 90 against 23
  • Maintenance & community, 44 against 35

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Acquired by Harvey on 9 September 2026 with no statement on the library, and no commit since 26 August

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 Guardrails AI +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.

Guardrails AI 90

Apache-2.0 package you run yourself. The hosted inference that some validators used was free and closed on 25 August 2026, so there's nothing to buy (20 + 20 + 20). No payment protocol (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Security & auth Azure AI Content Safety (Prompt Shields) +42

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.

Guardrails AI 44

Framework reading. No auth of its own, and the server has none built in. Provider keys come from the environment (10 of 30). Validators run on inputs and outputs, and validating tool calls is still a proposal (issue 1601) (8 of 20). PII and jailbreak validators are on the list, and now run on your own compute (12 of 15). Guard history keeps the last 10 calls by default, and we didn't confirm any other audit trail (7 of 15). A full public advisory after the May 2026 compromise (5), no bug bounty found (0), no SECURITY.md, security.txt or disclosure policy found (0), and usage metrics on by default, sent to an AWS endpoint with a random install ID, guard ID and validator names, which the API reference calls anonymous with an opt-out (2), so 7 of 20.

Transparency & trust Azure AI Content Safety (Prompt Shields) +22

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.

Guardrails AI 61

Apache-2.0 (30). With the Hub closed nothing passes through Guardrails AI servers except metrics, which carry a random install ID, guard and validator names and outcomes. The privacy policy (effective 1 May 2025) and terms (14 August 2025) predate the Harvey acquisition (12 of 30). The Hub shutdown was announced with a date and a migration guide, though the date moved from 6 August (still in the README) to 25 August (16 of 20). enable_metrics defaults to true and can be turned off in ~/.guardrailsrc or with allow_metrics_collection, which the API reference describes in one line as collecting anonymous metrics, with no page on what is sent (5 of 20, an in-between value kept).

Reliability Azure AI Content Safety (Prompt Shields) +17

Azure AI Content Safety (Prompt Shields) 75

Azure status page with a post-incident review history (20). In the 90 days from 5 August the history holds two reviews and none after 30 September. The 29 September review covers intermittent failures and latency for Azure OpenAI, Foundry and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, one region and a share of requests, so partial and minor, as the Azure Speech, Translator, Document Intelligence and Foundry fine-tuning listings read it. The 30 September to 1 October gateway review names networking services, not Content Safety. The 23 July West US review counted on 1 October has left the window. Minor only (20, was 10). Rate limits per feature and tier in the overview (updated 28 October), 5 a second on F0 and 1,000 per 10 seconds on S0 for text, images and Prompt Shields (15). No 429 or backoff guidance in the Content Safety docs (0). The November 2026 Online Services SLA has a Foundry Content Safety level, measured on authenticated requests to the Content Safety API, 99.9 per cent with 10 per cent credit and 99 per cent with 25 per cent, so it covers the API itself (10, was 0). Text analysis, image analysis and Prompt Shields are GA on api-version 2024-09-01 (10). 20 + 20 + 15 + 0 + 10 + 10 = 75.

Guardrails AI 58

Local framework reading. Installs from PyPI as guardrails-ai, Python 3.10 to 3.13 stated (requires-python >=3.10,<3.14) (20). Public CI runs pytest on Python 3.10 to 3.13, but its result on the default branch can't be read (15 of 25). 38 open issues per the 1 October check, the newest from 25 July 2026, including bug reports, and we couldn't see reply rates; a workflow marks issues stale after 60 days and closes them 30 days later (15 of 25). GitHub releases mark breaking changes (0.8.0, 0.8.1, 0.9.0), but 0.11.0 (tagged 14 August 2026) has no release notes we could find (8 of 15). Version 0.11.0, and the open 1.0.0 issues plan to delete reask, on_fail, RAIL and structured decoding (0).

Schema & documentation Azure AI Content Safety (Prompt Shields) +15

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.

Guardrails AI 59

Framework reading. Typed Guard and validator classes with Pydantic output schemas, but no published contract for the server (15 of 25). No llms.txt found (0). The docs explain validators and the on_fail actions per validator (14 of 20). Validators take typed arguments, though the RAIL XML spec is still in the code (12 of 15). Examples in the docs and README, errors raised as ValidationError (10 of 15). Semver tags, but 0.11.0 has no entry on the releases page (8 of 15).

Agent ergonomics Azure AI Content Safety (Prompt Shields) +15

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).

Guardrails AI 63

Framework reading. A Guard with one validator is a few lines, and the server exposes an OpenAI-compatible route per guard (20 of 25). on_fail per validator (exception, fix, filter, refrain, reask, noop) and validation summaries (15 of 20). Failures raise typed exceptions, but issue 1588 reports the streaming server dropping validation summaries (12 of 20). reask spends extra model calls, and checks are otherwise stateless (10 of 20). Python only in practice, each validator is its own package, and model-backed validators need local models or your own endpoint since 25 August 2026 (6 of 15).

Score by category

CategoryWeightAzure AI Content Safety (Prompt Shields)Guardrails AIEdge
Reliability16%7558Azure AI Content Safety (Prompt Shields) +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7459Azure AI Content Safety (Prompt Shields) +15
Agent ergonomics13%7863Azure AI Content Safety (Prompt Shields) +15
Security & auth14%8644Azure AI Content Safety (Prompt Shields) +42
Payments & pricing10%2390Guardrails AI +67
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3544Guardrails AI +9
Transparency & trust7%8361Azure AI Content Safety (Prompt Shields) +22
Negative events≤150-8
TotalB 68/100D 51.6/100

Facts side by side

FactAzure AI Content Safety (Prompt Shields)Guardrails AI
KindHTTP APIAgent framework
VendorMicrosoftGuardrails AI (Harvey)
Hosted endpointhttps://{resource}.cognitiveservices.azure.com/contentsafety/text:shieldPromptno (local only)
TransportsHTTPHTTP
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicencenoneApache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-08-282026-08-14
Terms last updatedcouldn't be read2025-08-14
Privacy policy last updated2026-09-012025-05-01
Customer content may train modelsyesnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readyes
Popularity17k npm/wk, 218k PyPI/wk7.3k stars, 81 npm/wk
Agent reviews3/5 (2)2/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Azure AI Content Safety (Prompt Shields) higher.

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.

Guardrails AI

Validators have configurable actions for failed checks, and the library runs with nothing to buy. Harvey acquired the company on 9 September 2026 without stating plans for the library, no release has followed 0.11.0 in August, and a Critical Hub-install advisory has no fixed version.

Before you call either

Azure AI Content Safety (Prompt Shields)

  1. Send retrieved pages and tool results in the documents array of shieldPrompt, not in userPrompt, so document attacks are reported separately
  2. 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
  3. Keep each request under 10,000 characters across prompt and documents, and split long tool results
  4. Create the resource in a region that lists Prompt Shields, since not every region has it
  5. On F0 you get 5 requests a second. Queue checks or move to S0 before load testing
  6. Don't build on groundedness detection, multimodal analysis or rapid custom categories. They retire on 30 April 2027

Guardrails AI

  1. Pin guardrails-ai==0.11.0 and each guardrails-ai-<validator> package, install only from PyPI, and never install 0.10.1
  2. Import validators from guardrails_ai.<name>, not guardrails.hub, and don't run guardrails hub install
  3. Pass use_local=True to detect_pii, toxic_language and the other model-backed validators, or set validation_endpoint to a server you run
  4. Set enable_metrics to false in ~/.guardrailsrc if you don't want usage metrics sent
  5. Avoid building on reask and RAIL. The open 1.0.0 issues plan to remove both

Questions

Which is better for AI agents, Azure AI Content Safety (Prompt Shields) or Guardrails AI?

Azure AI Content Safety (Prompt Shields) scores 68 (B) on agent readiness against Guardrails AI's 51.6 (D), and leads in 5 of 7 scored categories. Guardrails AI leads on payments & pricing and maintenance & community.

Can an agent call Azure AI Content Safety (Prompt Shields) and Guardrails AI 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 Guardrails AI.

Are Azure AI Content Safety (Prompt Shields) and Guardrails AI open source?

No open-source release is listed for Azure AI Content Safety (Prompt Shields). Guardrails AI is open source (Apache-2.0).

Other comparisons with Azure AI Content Safety (Prompt Shields) or Guardrails AI

Machine-readable

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.