Chirindo

Configure Chirindo for my MCP agent: block tool calls that delete databases, bulk export sensitive data, or send external network requests. When a policy is triggered, return a denial and generate a signed audit receipt.

A policy enforcement result where risky calls are denied, with verifiable signed receipts and audit log details.

Use Chirindo to protect my MCP tool boundary: allow reading public documents and querying the internal knowledge base, but generate a signed receipt for every approved tools/call request, recording timestamp, policy version, tool name, and parameter summary.

Compliant calls are forwarded normally, along with signed receipts and key audit fields for each call.

I need to review my AI agent’s MCP tool usage over the past week. Using Chirindo’s signed receipts, create an audit summary showing counts of denied and approved calls, the most frequently triggered policies, and whether the verifiable evidence chain is complete.

An audit summary covering call statistics, policy hits, and conclusions on evidence-chain completeness and verifiability.