Sign a single MPP voucher (48 bytes Borsh) and POST it to pay.sh.
AI agents use robot_sign_voucher_tick to commit financial operations through Execution Market — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool cryptographically signs a payment voucher and submits it to a payment endpoint. Signing and posting an MPP voucher constitutes committing a financial obligation — it authorizes a USDC payment on the Execution Market platform. Given the server context of 'Gasless USDC payments via x402,' a misused or forged voucher could result in unauthorized fund transfers.
From the tool's definition Sign a single MPP voucher (48 bytes Borsh) and POST it to pay.sh
Attacks that exploit this kind of access
Sign a single MPP voucher (48 bytes Borsh) and POST it to pay.sh. It is categorised as a Financial tool in the Execution Market MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Execution Market MCP server in PolicyLayer and add a rule for robot_sign_voucher_tick: 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 Execution Market. Nothing to install.
robot_sign_voucher_tick 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 robot_sign_voucher_tick 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 robot_sign_voucher_tick. 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.
robot_sign_voucher_tick is provided by the Execution Market MCP server (https://mcp.execution.market/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 →