Get recently issued proof bundles that demonstrate end-to-end verifiability. Each bundle contains a spend attestation token, GMV inclusion proof, and reward commitment — everything needed to independently verify a receipt's journey from scan to Bitcoin settlement. These are real production proofs...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Crinkl Commerce MCP server.
Free to start. No card required.
AI agents call get-recent-issued-proofs to retrieve information from Crinkl Commerce MCP without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get-recent-issued-proofs only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get-recent-issued-proofs": {}
}
}See the full Crinkl Commerce MCP policy for all 22 tools.
These attack patterns abuse exactly the kind of access get-recent-issued-proofs gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get recently issued proof bundles that demonstrate end-to-end verifiability. Each bundle contains a spend attestation token, GMV inclusion proof, and reward commitment — everything needed to independently verify a receipt's journey from scan to Bitcoin settlement. These are real production proofs, not test data. Note: rewardCommitmentToken and batchAnchor may be null for recent spends because reward commitments are batched asynchronously (typically within hours). The spend token and GMV inclusion proof are always present and independently verifiable. Check the 'steps' array and 'ok' field for per-step verification results.. It is categorised as a Read tool in the Crinkl Commerce MCP MCP Server, which means it retrieves data without modifying state.
Register the Crinkl Commerce MCP server in PolicyLayer and add a rule for get-recent-issued-proofs: 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 Crinkl Commerce MCP. Nothing to install.
get-recent-issued-proofs 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 get-recent-issued-proofs 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 get-recent-issued-proofs. 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.
get-recent-issued-proofs is provided by the Crinkl Commerce MCP server (https://mcp.crinkl.xyz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 22 Crinkl Commerce MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.