Approve the exact tool call.

• Install the gateSealInstall Seal, run the demo, then choose the tool calls that need approval.
• Check a receipt↗seal-checkOpen the browser checker to inspect the checks supported for your decision receipt.
• Review the evidenceseal-assurance-kitRun receipt, policy-coverage and conformance checks from the command line.

Decision receiptRecorded example

demo.mutate

Recorded decision: BLOCK

Document structure

Valid

Signature & bindings

Valid

Verifier-local replay

Reproduced

Operator authority

Not established

Event occurrence

Not established

Recorded result for the bundled public specimen, not a live check — open thebrowser checker guide to run this yourself against the example receiptand its demo public key.

How Seal fits into a tool call

Seal is a local approval gate for selected Claude Code MCP tool calls. Review the exact request, allow at most one execution per approval, and inspect a signed decision receipt.

Agent request → Seal approval gate → selected MCP tool (if permitted). Seal also writes a signed decision receipt; check that recorded evidence with the browser checker or the assurance CLI. Checking a receipt establishes what the check reports — it is not itself a claim that a tool effect occurred.

Start with the demo

The install and demo guide walks through a harmless approve-once demo and a refusal replay, so you can observe an approval and a refusal before protecting a real tool.

What the checks establish

The companion tools let you check recorded evidence separately from the running Seal deployment. The browser checker and CLI share kernel and receipt-format dependencies, so their agreement can also reflect a shared defect. A passing receipt check establishes only the properties it reports; it does not by itself establish operator identity or prove that a tool effect occurred.

Lean proofs cover specified decision-model properties. Seal currently documents that correspondence between its proved authorization model and shipped authorization path is neither tested nor proved. Read thecurrent assurance scope for the evidence and remaining assumptions.

Explore the documentation

• Operate Seal
• Understand receipts
• Troubleshoot a refusal
• Architecture and verification relationships