checklist_verify_run
Recomputes and checks a checklist run: every step receipt's execution_hash, the hash-chain link between consecutive steps, and (if a run_receipt is supplied) the §20.1 RFC 6962 Merkle root over every step. Returns valid:true/false, per-step ok/hash_ok/link_ok, and broken_at (the zero-based index ...
This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/checklist-verify-run.md
What checklist_verify_run does on Ainumbers Mcp Apps
AI agents call checklist_verify_run to retrieve information from Ainumbers Mcp Apps without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
run_receipt | object | — | The run receipt to check the Merkle root and its own execution_hash against. Omit to check only the step chain. |
step_receipts | array | Yes | Ordered array of step receipts, as returned by checklist_step_receipt. |
Parameters from the server's own tool schema.
Why checklist_verify_run is rated Low
This tool performs cryptographic verification of checklist run integrity by computing hashes and validating Merkle roots—pure read-only operations with no side effects. It retrieves or verifies existing data without altering state. The server description confirms 'Read-only, no auth, zero PII', further supporting Read classification.
From the tool's definition Tool name: checklist_verify_run. Description explicitly states it 'Recomputes and checks' and 'Returns valid:true/false, per-step ok/hash_ok/link_ok, and broken_at'. The verb 'checks' and 'returns' indicate data retrieval and verification only.
Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs checklist_verify_run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ainumbers Mcp Apps, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For checklist_verify_run, this is the rule to start with:
checklist_verify_run is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every checklist_verify_run call is checked against it from then on.
Questions about checklist_verify_run
Recomputes and checks a checklist run: every step receipt's execution_hash, the hash-chain link between consecutive steps, and (if a run_receipt is supplied) the §20.1 RFC 6962 Merkle root over every step. Returns valid:true/false, per-step ok/hash_ok/link_ok, and broken_at (the zero-based index of the first broken step, or null). Same recompute a human gets from the browser Run Verifier. It is categorised as a Read tool in the Ainumbers Mcp Apps MCP Server, which means it retrieves data without modifying state.
checklist_verify_run accepts 2 parameters: run_receipt, step_receipts. Required: step_receipts. The full parameter table on this page comes from the server's own tool schema.
Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for checklist_verify_run: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ainumbers Mcp Apps. Nothing to install.
checklist_verify_run is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the checklist_verify_run rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for checklist_verify_run. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
checklist_verify_run is provided by the Ainumbers Mcp Apps MCP server (postoaklabs/ainumbers-mcp-apps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ainumbers Mcp Apps, and thousands of servers like it.
This server
Across the catalogue