Create a zero-registration order via x402 pay-per-use. Requires TRON_PRIVATE_KEY.
AI agents use create_paid_order to commit financial operations through MERX - TRON Resource Exchange — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a financial transaction on the TRON blockchain using a private key to authorize payment. It commits financial obligations (pay-per-use) and moves crypto assets, making it Financial category. The use of a private key and blockchain payments elevates severity to critical, as misuse could drain funds or authorize unauthorized transactions.
From the tool's definition 'Create a zero-registration order via x402 pay-per-use. Requires TRON_PRIVATE_KEY.'
Attacks that exploit this kind of access
Create a zero-registration order via x402 pay-per-use. Requires TRON_PRIVATE_KEY. It is categorised as a Financial tool in the MERX - TRON Resource Exchange MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for create_paid_order: 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 MERX - TRON Resource Exchange. Nothing to install.
create_paid_order 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 create_paid_order 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 create_paid_order. 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.
create_paid_order is provided by the MERX - TRON Resource Exchange MCP server (Hovsteder/merx-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 →