protect-mcp-setup

You enforce policy control by applying Cedar policy evaluation to gate execution for Bash, Edit, Write, and WebFetch actions, automatically blocking unsafe Claude Code tool calls before they run.

You generate tamper-evident audit trails by creating Ed25519 signed receipts and applying hash chaining after each Claude Code tool call, producing compliance-ready evidence that supports offline verification.

Offline verification for signed receipts is the cryptographic validation of Ed25519 signatures and hash chains from agent workflows without network access, proving tool call decisions and outputs remain untampered.

Yes, Cedar policy evaluation works with Claude Code Bash and Edit actions by intercepting those tool calls to check permissions and block non-compliant execution before it happens.

You need cryptographic receipts for Claude Code automation when operating in regulated environments or compliance workflows that require tamper-evident, offline-verifiable evidence of agent actions during code changes.

Yes, you can use Ed25519 signing and hash chaining to produce compliance-ready evidence, replacing ad hoc trust with cryptographically signed receipts that prove the integrity of each tool invocation.