Settle outstanding spend receipts into a Merkle-rooted settlement batch.
AI agents use meter_settle to commit financial operations through Verifiedstate — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Settlement of spend receipts is a financial operation that commits and finalizes outstanding payment obligations. This is irreversible in financial terms — once settled into a batch, the financial commitments are locked. The tool sits alongside meter_spend, meter_authorize, and meter_budget, confirming this is part of a billing/payment pipeline. Misuse could result in incorrect or fraudulent financial settlements.
From the tool's definition 'Settle outstanding spend receipts into a Merkle-rooted settlement batch' — settling spend receipts is a financial commitment/reconciliation operation that finalizes monetary obligations
Attacks that exploit this kind of access
Settle outstanding spend receipts into a Merkle-rooted settlement batch. 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_settle: 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_settle 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_settle 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_settle. 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_settle 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 →