Create a Proof Meter capability that grants an agent a spend budget. Returns a signed capability token.
AI agents use meter_authorize to commit financial operations through Verifiedstate — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates a financial authorization/capability that grants spending power to an agent. While it does not immediately move money, it establishes a signed, cryptographically-backed budget authority that directly enables financial obligations. Under the rule that Financial > all other categories, and because misuse could authorize excessive spend budgets, this is classified as Financial with high severity.
From the tool's definition "grants an agent a spend budget" and "Proof Meter capability" — this tool creates an authorization that commits financial spending limits, returning a "signed capability token" that enables future financial transactions
Attacks that exploit this kind of access
Create a Proof Meter capability that grants an agent a spend budget. Returns a signed capability token. 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_authorize: 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_authorize 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_authorize 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_authorize. 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_authorize 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 →