check_action
Check a proposed action against enforcement rules to obtain a compliance receipt for destructive operations or receive structured violation warnings.
Instructions
v0.11.3 · the protocol enforcement point. Pass a proposed action description + its category; the server matches against rule memories (type=rule) and either:
APPROVES: returns a short-lived Compliance Receipt (HMAC-signed, 60s default) the agent can pass to destructive tools (e.g. delete_memory) as proof of compliance.
DENIES: returns structured hard_violations (severity:hard rules that block) and/or soft_warnings (severity:soft rules that warn but allow).
Tier 1 (deterministic) matches the action against rule.matches regexes + rule.enforce_on category filter. Works on every MCP client. Tier 2 (v0.11.7+) calls back to the client via MCP sampling/createMessage to judge rule.applies_when natural-language conditions. Auto-enabled on clients that declared the sampling capability; silently skipped on clients that didn't.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | Description of the proposed action. Plain prose · 'delete the memory called X', 'push to main branch', 'commit with message Y', etc. | |
| session_id | No | Optional session identifier · binds the issued receipt to this session via a caveat. | |
| action_type | Yes | Action category for rule.enforce_on matching. Examples: 'deletions', 'commits', 'pushes', 'file_writes', 'chat_responses', 'tool_calls'. | |
| use_sampling | No | Opt out of Tier-2 Sampling enrichment (default true). Set false for batched/scripted use where the Sampling round-trip would add latency. CLI invocations default this to false automatically. |