This is an enterprise engagement, not a self-serve setting. BotShield’s professional services team sets up and runs the policy service with your security and IT teams. To start, email hello@botshield.ai.
Where the hooks are
The Claude Enterprise inference hook is the broadest of these: it runs on Anthropic’s servers, so it covers every Claude product in the organization with nothing installed on employee devices. The others run where the agent runs, so they’re a good fit for developer tools and for agents your own teams build.
How it works with Claude Enterprise inference hooks
Your admin points the organization’s inference hook at a BotShield policy endpoint and turns on Validate tool calls. You agree with us which tools need a person: for example, any tool that moves money, sends email to customers, or changes production data. Step by step:- The tool call arrives. Anthropic sends BotShield the tool call frame before any tool in that response runs. One verdict covers all the tool calls in the response.
- BotShield checks the policy. Tools that don’t need a person get an immediate allow, so normal work isn’t slowed down.
- No approval yet: deny and ask. The hook has to answer within the timeout your admin sets (5 seconds by default, 10 seconds at most), which isn’t long enough for someone to find their phone. So BotShield answers deny, with a
deny_reasontelling the person to approve in the BotShield app, and sends the request to their phone at the same moment. - The person confirms. They see what the AI is about to do and confirm with their passkey, or decline.
- The retry goes through. When the person asks Claude to continue, the same tool call comes back. BotShield finds the matching approval and answers allow. Each approval covers one action, once, for a short time.
What BotShield receives and keeps
The inference hook sends the conversation transcript and anactor with an account ID and an email address. BotShield uses the account ID to find the phone bound to that account, keeping only a keyed hash of it, and doesn’t store the email address or the transcript. What BotShield keeps is the same as everywhere else: an approval record tied to an opaque ID, the action that was confirmed, and when. See Privacy boundary.
Limits to plan around
- Claude Enterprise only. Inference hooks aren’t available to Claude Platform (API) organizations, or on Amazon Bedrock or Google Cloud.
- Deny, then retry. The hook can only answer allow or deny, so the person sees one blocked attempt before the approved one.
- Failure handling is your admin’s choice. If the policy endpoint can’t be reached, Anthropic applies your organization’s failure setting: block, or allow without inspection. For tools that need a person, we recommend block.
- Roll out in shadow mode first. Inference hooks support shadow mode, a rollout percentage and role exclusions, so you can watch verdicts on live traffic before anything is blocked.
How it works with Claude Code and Codex hooks
Claude Code and Codex both run aPreToolUse hook before a tool executes, and both let IT lock hooks in place so engineers can’t turn them off: managed settings for Claude Code, and requirements.toml or the workspace’s Agent Security settings for Codex.
The flow matches the one above. The hook matches the tools that need a person (for example mcp__payments__.*), calls the BotShield policy endpoint, and either lets the call run or blocks it with a reason while the request goes to the person’s phone.
How this fits with other BotShield integrations
These work together. A tool that checks BotShield itself keeps doing so, and the hook adds coverage for the tools that don’t.
Talk to us
Implementation is handled by BotShield’s sales and professional services team. We’ll help you:- choose which tools and teams need the account holder’s approval;
- set up the policy endpoint, signing secret and failure handling with your security team;
- link employees’ BotShield apps to your organization;
- roll out in shadow mode, then turn on enforcement.
