Buy energy or bandwidth on Merx. Routed to cheapest provider. Auth required.
AI agents use create_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 executes a financial purchase of TRON resources (energy or bandwidth). It commits real funds on a blockchain exchange, qualifying it as a Financial category action. Misuse by an AI agent could result in unauthorized spending of cryptocurrency, hence high severity.
From the tool's definition 'Buy energy or bandwidth on Merx' — the tool purchases resources, committing financial obligations on the TRON network. 'Routed to cheapest provider' confirms an actual marketplace transaction.
Attacks that exploit this kind of access
Buy energy or bandwidth on Merx. Routed to cheapest provider. Auth required. 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_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_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_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_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_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 →