Cryptographically verify a Proof Meter spend receipt (hash, signature, chain, Merkle inclusion).
AI agents call meter_verify to retrieve information from Verifiedstate without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs cryptographic verification of existing receipts—a pure read operation with no side effects. It queries and validates data structures but does not create, modify, delete, execute arbitrary code, or move financial value. The verification itself is a read-only integrity check.
From the tool's definition Tool description states 'Cryptographically verify' which is a read-only verification operation that checks cryptographic properties and Merkle inclusion of an already-created spend receipt. No state is modified.
Attacks that exploit this kind of access
Cryptographically verify a Proof Meter spend receipt (hash, signature, chain, Merkle inclusion). It is categorised as a Read tool in the Verifiedstate MCP Server, which means it retrieves data without modifying state.
Register the Verifiedstate MCP server in PolicyLayer and add a rule for meter_verify: 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 Verifiedstate. Nothing to install.
meter_verify 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 meter_verify 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 meter_verify. 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.
meter_verify is provided by the Verifiedstate MCP server (verifiedstate/verifiedstate-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 →