skills.rest
ArogyaReddy
ArogyaReddyCOMMUNITY
Explore all skills by this author →
GitHub

protect-mcp-setup

Enforce Cedar policies and generate Ed25519-signed receipts for Claude Code tool calls.

Updated Apr 19, 2026
Search Tags:#audit#compliance#receipts#cryptography#policy#claude-code#cedar
One-click install
npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill protect-mcp-setup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: protect-mcp-setup
Source: https://github.com/ArogyaReddy/https-github.com-wshobson-agents/tree/main/plugins/protect-mcp/skills/protect-mcp-setup
Command: npx skills add https://github.com/ArogyaReddy/https-github.com-wshobson-agents --skill protect-mcp-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cryptographic governance for Claude Code tool calls by applying Cedar policies and producing Ed25519-signed receipts that can be verified offline.

Core Features & Use Cases

  • Policy enforcement: Evaluate every tool invocation against Cedar policies before execution to prevent unsafe actions.
  • Tamper-evident receipts: Generate signed receipts containing tool name, inputs, outputs, decision, policy digest, and timestamp, hash-chained for integrity.
  • Offline verification: Receipts can be verified without network access using veritasacta tools, enabling auditable records for compliance.
  • Use Case: For regulated projects, attach receipts to session logs to prove tool decisions and actions for audits.

Quick Start

Use the protect-mcp skill to enable policy enforcement and signed receipts for Claude Code tool calls.

Frequently Asked Questions about protect-mcp-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce Cedar policies on Claude Code tool calls?▼

To enforce Cedar policies on Claude Code tool calls, you can use PreToolUse hooks to evaluate every tool invocation against your defined policies before execution, preventing unsafe actions automatically.

Can I generate cryptographically signed receipts for Claude Code actions offline?▼

Yes, you can generate Ed25519-signed receipts for Claude Code actions that are fully verifiable offline. These tamper-evident receipts contain tool names, inputs, outputs, decisions, and timestamps for audit compliance.

What's the best way to audit Claude Code tool decisions for regulated projects?▼

The best way to audit Claude Code tool decisions for regulated projects is attaching hash-chained cryptographic receipts to session logs, proving tool decisions and actions for compliance reviews without requiring network access.

Do I need PreToolUse and PostToolUse hooks to verify tool actions cryptographically?▼

Yes, PreToolUse and PostToolUse hooks are required to evaluate Cedar policies before execution and generate Ed25519-signed receipts with local storage after tool actions complete.

How does offline verification work for signed tool call receipts?▼

Offline verification works by using veritasacta tools to check Ed25519-signed, hash-chained receipts containing tool inputs, outputs, policy digests, and timestamps without needing any network access.

Related Skills

Explore More Legal & Compliance Skills→
AvaTar-ArTsAvaTar-ArTs

hook-development

Define and validate event-driven hooks for Claude Code plugins.

Community
Advanced
haxlyshaxlys

protect-mcp-setup

Enforce Cedar policies and generate Ed25519-signed receipts for Claude Code tool calls.

Community
Advanced
ArogyaReddyArogyaReddy

signed-audit-trails-recipe

Generate Ed25519 receipts for Claude Code tool calls with Cedar policy evaluation.

Community
Advanced
gounthargounthar

aptos-move-prover

Prove Move smart contract properties with Move Prover and MSL.

Community
Advanced