Critical Risk →

cancel_standing_order

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).

Part of the MERX - TRON Resource Exchange MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

merx-mcp Destructive

AI agents may call cancel_standing_order to permanently remove or destroy resources in MERX - TRON Resource Exchange. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call cancel_standing_order in a loop, permanently destroying resources in MERX - TRON Resource Exchange. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

merx-tron-resource-exchange.yaml
tools:
  cancel_standing_order:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full MERX - TRON Resource Exchange policy for all 66 tools.

Tool Name cancel_standing_order
Category Destructive
Risk Level Critical

View all 66 tools →

Agents calling destructive-class tools like cancel_standing_order have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

cancel_standing_order is one of the critical-risk operations in MERX - TRON Resource Exchange. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the cancel_standing_order tool do? +

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.

How do I enforce a policy on cancel_standing_order? +

Add a rule in your Intercept YAML policy under the tools section for cancel_standing_order. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the MERX - TRON Resource Exchange MCP server.

What risk level is cancel_standing_order? +

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.

Can I rate-limit cancel_standing_order? +

Yes. Add a rate_limit block to the cancel_standing_order rule in your Intercept 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.

How do I block cancel_standing_order completely? +

Set action: deny in the Intercept 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.

What MCP server provides cancel_standing_order? +

cancel_standing_order is provided by the MERX - TRON Resource Exchange MCP server (merx-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.