protect-mcp-setup
Sets up Cedar policy enforcement and Ed25519 signed receipts for Claude Code tool calls.
- Kind
- Skill
- Works with
- Claude Code, Codex
- Source
- wshobson/agents @ 0874a27b17a2
- Path
- plugins/protect-mcp/skills/protect-mcp-setup/SKILL.md
- License
- MIT
- Jobs
- Guardrails
InstallInstall it from a plugin marketplace.
/plugin install protect-mcp@claude-code-workflows
# protect-mcp — Policy Enforcement + Signed Receipts Cryptographic governance for every Claude Code tool call. Each invocation is evaluated against a Cedar policy and produces an Ed25519-signed receipt that anyone can verify offline. ## Overview Claude Code runs powerful tools: `Bash`, `Edit`, `Write`, `WebFetch`. By default there is no audit trail, no policy enforcement, and no way to prove what was decided after the fact. `protect-mcp` closes all three gaps: - **Cedar policies** (AWS's open authorization engine) evaluate every tool call before execution. Cedar deny is authoritative. - **Ed25519 receipts** record the name of each tool that ran, signed with your key. - **Offline verification** via `npx @veritasacta/verify`. No server, no account, no trust in the operator. ## Problem AI agents make decisions that affect money, safety, and rights. The Claude Code session log records what happened, but the log is: - Mutable — anyone with access can edit it - Unsigned — there is no way to prove integrity - Operator-bound — verification requires trusting whoever holds the log For compliance contexts (finance, healthcare, regulated research), this is not …