Cancel a standing order by its UUID. The order is moved to CANCELLED status and will not trigger again. Already-executed actions are NOT reversed. Auth required (API key).
AI agents call cancel_standing_order to permanently remove resources in MERX - TRON Resource Exchange — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a standing order is irreversible — the order is permanently moved to CANCELLED status and cannot be re-triggered. The description explicitly states already-executed actions are not reversed, confirming no rollback is possible. This qualifies as Destructive.
From the tool's definition 'Cancel a standing order by its UUID. The order is moved to CANCELLED status and will not trigger again. Already-executed actions are NOT reversed.'
Attacks that exploit this kind of access
Cancel a standing order by its UUID. The order is moved to CANCELLED status and will not trigger again. Already-executed actions are NOT reversed. Auth required (API key). It is categorised as a Destructive tool in the MERX - TRON Resource Exchange MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MERX - TRON Resource Exchange MCP server in PolicyLayer and add a rule for cancel_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.
cancel_standing_order is a Destructive 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 cancel_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 cancel_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.
cancel_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 →