Create a server-side standing order with trigger-based automation. Auth required.
AI agents use create_standing_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.
A standing order in a resource exchange context (TRON blockchain) automates repeated financial transactions. Misuse by an AI agent could result in repeated unauthorized transfers of funds or resources, making this a Financial category tool with critical severity due to its automated, recurring nature and potential for significant financial loss.
From the tool's definition 'Create a server-side standing order with trigger-based automation' — standing orders are recurring financial commitments that automatically move funds/resources on a schedule or trigger.
Attacks that exploit this kind of access
Create a server-side standing order with trigger-based automation. 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_standing_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_standing_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_standing_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_standing_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_standing_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 →