All blog posts

Anthropic just gave security teams a way to inspect and block AI prompts before the model ever sees them — enforced on Anthropic’s own servers, with nothing to install on anyone’s laptop. For security vendors, it’s also a brand-new surface to build products on.

---

Since the first employee pasted a customer record into a chat window, security teams have wanted one thing: a way to catch it before it leaves the building. Inference Hooks — now in beta for Claude Enterprise organizations — turn governing Claude usage from an after-the-fact audit problem into a real-time, inline decision.

Here’s what it is, why it matters for security companies, and where the sharp edges are.

---

What Inference Hooks Actually Do

The mechanic is simple, and that’s the point.

1. A user submits a prompt on a governed surface — claude.ai, Cowork, or Claude Code (web, desktop, or CLI).
2. Before inference runs, Anthropic sends an HTTPS POST containing the conversation transcript to an endpoint your organization configures — an AI security server that you, or your security vendor, operate.
3. Your server evaluates the content and returns a verdict: allow or deny.
4. On allow, inference proceeds. On deny, the request never reaches the model, the user sees a blocked-by-policy message, and the denial is logged to the organization’s Activity Feed.

The verdict is a tiny JSON object. A denial can carry a deny_reason (shown to the user, up to 500 characters) and a reference_id (your own opaque evaluation ID, recorded on the compliance event so you can join denials back to your own system).

{
  "action": "deny",
  "deny_reason": "This prompt appears to contain customer payment card data, which your organization's policy does not allow.",
  "reference_id": "scan_01HXPT4R9V"
}

Because the hook fires on Anthropic’s servers — after the request leaves the client and before the model runs — it applies uniformly to every governed request. No browser extension, no endpoint agent, no per-device rollout. One hook governs the whole organization.

Today there’s a single hook event, prompt, fired once per governed request before inference. Response-side enforcement — inspecting what Claude says back — is on the roadmap but not here yet.

---

Why This Matters for Security Companies

This is the interesting part. Inference Hooks aren’t just a config toggle — they’re a platform to build on. Anthropic defines the wire protocol; the actual policy logic is a server you build. That opens several product angles.

Inline DLP for AI, Finally at the Right Layer

Data Loss Prevention has always struggled with “shadow AI.” Employees paste source code, customer PII, or regulated data into chat tools, and traditional DLP either misses it — SaaS traffic looks like ordinary HTTPS — or blocks the whole tool bluntly. Inference Hooks let a DLP vendor receive the exact transcript: user text, tool calls, tool results, and extracted attachment text. Forward it to your existing scanner, deny anything carrying regulated material, and return a human-readable reason telling the user what to remove. Anthropic calls this out as the most common deployment.

Push-Based Transcript Archival

Want a real-time record of every AI conversation for compliance or eDiscovery? Run an always-allow server: return an allow verdict unconditionally and persist the frame after responding. It’s a push-based alternative to polling the Compliance API — you get transcripts as they happen, and answering before you persist keeps your round trip out of the user’s critical path.

Policy Engines Beyond DLP

The verdict server can enforce any rule you can compute from a transcript: model allowlists (deny unapproved models), project- or working-hours restrictions, and prompt telemetry — measuring how the org actually uses Claude at the moment of use, not from logs after the fact.

A Managed, Signed, Standardized Integration

For a vendor, the operational story is clean:

• Requests are signed per the Standard Webhooks spec — HMAC-SHA256 over {webhook-id}.{webhook-timestamp}.{body} — so you can cryptographically verify each request came from Anthropic.
• Traffic originates from a published IP block (160.79.106.0/24) you can allowlist.
• webhook-id doubles as an idempotency key for deduplication.
• Denials carry your reference_id into the customer’s Activity Feed, so your product’s findings join cleanly to Anthropic’s audit trail.

You’re building against a documented, stable-ish contract — not scraping or reverse-engineering a chat product.

Safe, Staged Rollout Is Built In

Security tooling lives or dies on whether it can deploy without breaking the business. Inference Hooks ship with shadow mode (observe verdicts on live traffic without blocking), a rollout percentage (inspect a chosen fraction of requests), and role exclusions (exempt chosen roles entirely). A vendor can onboard a customer in observe-only mode, tune against real traffic, and flip to enforcement with confidence — the classic DLP playbook, supported natively.

---

The Pros and the Limitations

Inference Hooks are powerful but deliberately narrow. Weigh both sides before you build — or pitch — on them.

✅ Pros

• Right layer, right time. Enforcement happens server-side, before the model runs, so a denied prompt genuinely never reaches Claude.
• Nothing to deploy on endpoints. One org-wide hook covers claude.ai, Cowork, and Claude Code across web, desktop, and CLI.
• Rich, structured input. Your server sees the transcript as the user sees it — text, tool calls, tool results, extracted attachment text — with a forward-compatible content model.
• Strong trust boundary. Standard Webhooks signing, a five-minute timestamp tolerance against replays, a fixed egress IP range, and idempotency keys are all part of the contract.
• Operationally cautious by design. Configurable failure handling, a circuit breaker, shadow mode, and percentage rollout reduce the “security tool took down productivity” risk.
• Composable. It’s just an HTTPS server returning JSON — point it at your existing DLP scanner, SIEM, or policy engine.

❌ Limitations — Read Before You Pitch

• Claude Enterprise only. Platform / API organizations are explicitly out of scope, and it doesn’t apply to Claude on Amazon Bedrock or Google Cloud.
• Text only — no raw bytes, ever. Attachments arrive as metadata plus extracted text, so image-only content is invisible: a screenshot of a sensitive document or a scanned PDF with no text layer won’t be inspected.
• Allow or deny only. There is no redaction or rewriting — you can’t strip the card number and let the rest through. It’s all or nothing per prompt.
• Prompt-side only, for now. No response-side hook yet, so you can’t inspect or block what Claude outputs.
• You add latency to every governed request. Your full round trip is now in the critical path of every prompt. Default timeout is 5s (configurable 1–10,000 ms); a slow server means slow Claude for everyone.
• Fail-open vs. fail-closed both hurt. If your server errors or times out, the org either blocks all AI usage or lets prompts through uninspected. There’s no free lunch.
• The circuit breaker can silently stop enforcement. Sustained failures trip a breaker that halts calls to your server until an admin manually re-enables it — a flaky server can quietly disable your control.
• Big bodies. Transcripts are sent untruncated, up to 10 MB. Common defaults (nginx 1 MB, Express 100 KB) reject these, and a rejected body counts as a failure — under fail-open, the prompt reaches the model uninspected.
• source.application is advisory. Don’t rest a security-critical decision on which app claims to be calling.

---

Inference Hooks vs. the Compliance API

Anthropic is clear these are complementary, not competing. Use Inference Hooks to stop a request; use the Compliance API to audit what happened. A mature deployment uses both — prevention at the front door, forensics behind it.

	Inference Hooks	Compliance API
When	Inline, before inference runs	After the fact
What	Allows or denies each request in real time	Retrieves activity, chats, files, projects, users for audit & export
Direction	Anthropic calls your server	You call Anthropic’s API

---

The Bottom Line

Your Uptime Is the Customer’s AI Availability

Inference Hooks are a genuine shift in how enterprise AI gets governed: a real-time, server-side, org-wide control point that vendors can build on, with a clean signed protocol and a deployment model that respects how cautiously security tooling has to roll out.

The limits matter just as much. It’s prompt-side, allow/deny-only, text-only, Enterprise-only, and it sits in the latency path of every conversation. It is not a redacting proxy, it won’t catch a screenshot, and a fragile verdict server is a liability rather than a safeguard.

For security companies the opportunity is concrete — DLP-for-AI at the correct layer, real-time archival, custom policy enforcement — shipped as an HTTPS server that returns a two-field JSON object. The teams that win here will be the ones that build a fast, resilient, correctly-configured verdict server.

---

Based on Anthropic’s Inference Hooks documentation — platform.claude.com/docs/en/manage-claude/inference-hooks. Inference Hooks are in beta; field names, request shapes, and headers may change before general availability.