AI agents call verify_receipt to retrieve information from Verify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs cryptographic verification of artifacts against public keys. This is purely a read operation with no side effects: it does not modify data, execute external code, delete anything, or move funds. It retrieves and checks the validity of existing signed data. Severity is low because misuse by an AI agent (e.g., verifying untrusted artifacts) poses no direct harm to the user's system or data.
From the tool's definition Tool description states 'Verify a single signed artifact or receipt' — verification is a read-only operation that checks cryptographic signatures without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Verify a single signed artifact or receipt using an explicit public key or any embedded public key. It is categorised as a Read tool in the Verify MCP Server, which means it retrieves data without modifying state.
Register the Verify MCP server in PolicyLayer and add a rule for verify_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 Verify. Nothing to install.
verify_receipt 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 verify_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.
Set action: deny in the PolicyLayer policy for verify_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.
verify_receipt is provided by the Verify MCP server (scopeblind/verify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →