protect-mcp-governance

Evaluate Cedar policies for MCP tool calls and generate Ed25519 audit receipts.

27|5|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Fandry96/k3-agentic-skills --skill protect-mcp-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: protect-mcp-governance
Source: https://github.com/Fandry96/k3-agentic-skills/tree/main/skills/protect-mcp-governance
Command: npx skills add https://github.com/Fandry96/k3-agentic-skills --skill protect-mcp-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides governance over MCP tool calls by authoring Cedar policies and generating verifiable Ed25519 receipts to ensure traceability and auditability.

Core Features & Use Cases

  • Cedar policy authoring: write and test access-control rules for MCP tool calls.
  • Shadow-mode observation: observe decisions without blocking to validate policy behavior.
  • Enforce-mode protection: switch to blocking disallowed calls once policies are validated.
  • Receipts & verification: generate cryptographic receipts for each decision and verify them offline.

Quick Start

Configure a Cedar policy, initialize the MCP gateway, and run in shadow mode to observe decisions before enforcement.

Frequently Asked Questions about protect-mcp-governance

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

FAQPage Schema
How do I govern MCP tool calls with Cedar policies?

You can govern MCP tool calls by authoring Cedar access-control policies, initializing an MCP gateway, and running evaluations to produce verifiable Ed25519 receipts for auditing tool execution.

What is shadow-mode governance for MCP deployments?

Shadow-mode governance observes Cedar policy decisions on MCP tool calls without blocking them, allowing you to validate policy behavior safely before switching to enforce-mode blocking.

Can I generate cryptographic receipts for MCP tool call auditing?

Yes, the skill generates Ed25519 cryptographic receipts for each policy decision during MCP tool execution, which you can verify offline to ensure traceability and auditability.

How do I test access-control rules for MCP gateways before enforcement?

You write and test Cedar policies by running the MCP gateway in shadow mode, observing policy decisions on tool calls without blocking them to validate behavior before enforcement.

Do I need a specific MCP gateway setup to enforce Cedar policies?

Yes, you require a configured MCP gateway setup and Cedar policy files to evaluate access-control rules, generate signed receipts, and transition from shadow-mode observation to enforce-mode blocking.