List and filter Proof Meter spend receipts for a namespace.
AI agents call meter_receipts 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 queries historical billing records (receipts) for a namespace. It is purely informational — reading and filtering existing data without creating, modifying, deleting, or executing any external operations. The sibling tools like meter_spend (Write/Execute), meter_settle (Financial), and meter_authorize (Execute) are more severe; this one simply retrieves attestations of past transactions.
From the tool's definition Tool description states 'List and filter Proof Meter spend receipts' — a retrieval and query operation with no modification or side effects.
Attacks that exploit this kind of access
List and filter Proof Meter spend receipts for a namespace. 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_receipts: 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_receipts 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_receipts 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_receipts. 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_receipts 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 →