Record a spend event against a Proof Meter capability. Returns a signed, hash-chained receipt.
AI agents use meter_spend to commit financial operations through Verifiedstate — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool explicitly records a spend event, which constitutes committing a financial obligation or expenditure against a metered billing capability. The signed, hash-chained receipt further confirms this is a financial transaction with real billing consequences. Misuse by an AI agent could result in unauthorized charges or financial commitments, warranting high severity.
From the tool's definition "Record a spend event against a Proof Meter capability" and "Returns a signed, hash-chained receipt" — this tool commits financial spending/billing events
Attacks that exploit this kind of access
Record a spend event against a Proof Meter capability. Returns a signed, hash-chained receipt. It is categorised as a Financial tool in the Verifiedstate MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Verifiedstate MCP server in PolicyLayer and add a rule for meter_spend: 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_spend is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the meter_spend 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_spend. 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_spend 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.
meter_spend is one line of Verifiedstate's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →