Inference hooks rollout checklist

WorksheetInference hooks rollout checklist

Signal Over Noise · Inference hooks rollout checklist

For the security team at a Claude Enterprise company. Tick each item as you do it, write your answers in the boxes, then print the sheet or save it as a PDF.

Before you switch it on

Ask your security vendor whether its product supports Claude’s inference hooks. Vendor, contact and answer

Decide who runs the security server that answers allow or deny: your team or the vendor. Who runs it

Find your Owner or Primary owner. Only those roles can switch inference hooks on. Name

Decide whether to switch on Validate tool calls, so Claude’s use of connectors, skills and plugins is checked as well as prompts. Yes or no, and why

Decide what happens when your server fails

If your server is down or slow, should Claude block everything or carry on unchecked? Anthropic waits five seconds by default. Our choice, and who agreed it

Start in shadow mode

Run in shadow mode first, which records what would have been denied without blocking anything. How long, and who reviews the results

Use the rollout percentage to check a share of requests while you tune the rules. Starting percentage

Write the message staff see when something is blocked, including who to ask for an exception. Our message

Cover the gaps

Tell staff that screenshots of client documents go to Claude unchecked, so the same rules apply to them.

Tell staff that a blocked message stays in the chat, so they need to edit it out or start a new chat.

Don’t rely on hooks alone for voice mode. Anthropic says a small share of voice tool calls aren’t sent to your server.

Block personal Claude accounts in Claude Desktop on company computers.

List any Claude use outside your Enterprise account, such as Amazon Bedrock, Google Cloud or the Claude Platform API, which the hooks don’t cover. Where, and who checks it

Nothing ticked yet.

This page sends nothing anywhere. Your answers stay in your browser until you close it.