checklist_step_receipt

SERVERAinumbers Mcp Apps SOURCEpostoaklabs/ainumbers-mcp-apps

High RISK CLASS

Category Execute

Parameters 74 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/postoaklabs-ainumbers-mcp-apps/checklist-step-receipt.md

WHAT IT DOES

What checklist_step_receipt does on Ainumbers Mcp Apps

AI agents invoke checklist_step_receipt to trigger actions in Ainumbers Mcp Apps. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`step`	object	Yes	The step object from the definition's steps[] array being completed.
`evidence`	object	—	Evidence payload, e.g. { text_digest }, { file_sha256 }, or { attestation_digest }. Required unless evidence_requirement is "none".
`timestamp`	string	Yes	ISO 8601 completion timestamp (caller-supplied for determinism).
`step_index`	integer	Yes	Zero-based index of this step in the definition.
`completer_key`	string	—	Identifier of who/what completed the step (e.g. an agent id). Never real PII.
`definition_digest`	string	Yes	The definition_digest from checklist_validate_definition.
`prev_step_receipt_digest`	string	—	execution_hash of the previous step's receipt. Omit for the first step in the run.

Parameters from the server's own tool schema.

RISK

Why checklist_step_receipt is rated High

Although the server claims 'read-only' and 'zero PII', this tool's function—executing and recording deterministic procedural steps in a compliance/fintech workflow—constitutes an Execute category action. It performs side effects (state recording via receipts, digest chain updates, blocking-gate logic) triggered by caller arguments.

From the tool's definition Tool description states it 'Completes ONE step of a checklist/SOP run' and 'returns its OCG v0.4 step receipt' with execution tracking via digest chaining.

Risk signalsHigh parameter count (13 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs checklist_step_receipt 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_step_receipt, this is the rule to start with:

checklist_step_receipt Rate-limited

checklist_step_receipt stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "checklist_step_receipt": {
      "limits": [
        {
          "counter": "checklist_step_receipt_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Ainumbers Mcp Apps, apply this rule, and every checklist_step_receipt call is checked against it from then on.

FAQ

Questions about checklist_step_receipt

What does the checklist_step_receipt tool do? +

Completes ONE step of a checklist/SOP run and returns its OCG v0.4 step receipt: execution_hash chains to prev_step_receipt_digest (pass the previous step's execution_hash, or omit for step 0). A blocking-gate step with evidence_requirement != "none" and no evidence supplied is refused (the caller enforces step order; this tool enforces the evidence requirement per step). Call once per step in order, then pass the full ordered list of returned receipts to checklist_verify_run to check the chain and mint the run receipt. It is categorised as a Execute tool in the Ainumbers Mcp Apps MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does checklist_step_receipt accept? +

checklist_step_receipt accepts 7 parameters: step, evidence, timestamp, step_index, completer_key, definition_digest, prev_step_receipt_digest. Required: step, timestamp, step_index, definition_digest. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on checklist_step_receipt? +

Register the Ainumbers Mcp Apps MCP server in PolicyLayer and add a rule for checklist_step_receipt: 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.

What risk level is checklist_step_receipt? +

checklist_step_receipt is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit checklist_step_receipt? +

Yes. Add a rate_limit block to the checklist_step_receipt 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.

How do I block checklist_step_receipt completely? +

Set action: deny in the PolicyLayer policy for checklist_step_receipt. 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.

What MCP server provides checklist_step_receipt? +

checklist_step_receipt 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.

KEEP EXPLORING

More on Ainumbers Mcp Apps, and thousands of servers like it.

This server

All 689 Ainumbers Mcp Apps tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →