Critical Risk →

ibkr_global_cancel

Cancel all active IBKR orders. Requires confirm=true.

How to control ibkr_global_cancel ↓

What ibkr_global_cancel does on Ibkr

AI agents call ibkr_global_cancel to permanently remove resources in Ibkr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why ibkr_global_cancel needs a policy

Canceling all active orders is a destructive operation that cannot be undone and has immediate financial consequences. It irreversibly terminates trading positions and commitments. While requiring confirm=true provides a safeguard, the tool itself performs an irreversible action affecting potentially significant financial positions.

From the tool's definition Tool name 'ibkr_global_cancel' and description 'Cancel all active IBKR orders' indicate irreversible termination of multiple standing orders.

Documented attack patterns abuse exactly the kind of access ibkr_global_cancel gives an agent:

How to control ibkr_global_cancel

PolicyLayer is an MCP gateway — it sits between your AI agents and Ibkr, and nothing reaches the server without passing your rules. This is the rule we recommend for ibkr_global_cancel:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "ibkr_global_cancel"
  ]
}

ibkr_global_cancel disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ibkr — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about ibkr_global_cancel

What does the ibkr_global_cancel tool do? +

Cancel all active IBKR orders. Requires confirm=true. It is categorised as a Destructive tool in the Ibkr 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 ibkr_global_cancel? +

Register the Ibkr MCP server in PolicyLayer and add a rule for ibkr_global_cancel: 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 Ibkr. Nothing to install.

What risk level is ibkr_global_cancel? +

ibkr_global_cancel 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 ibkr_global_cancel? +

Yes. Add a rate_limit block to the ibkr_global_cancel 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.

How do I block ibkr_global_cancel completely? +

Set action: deny in the PolicyLayer policy for ibkr_global_cancel. 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 ibkr_global_cancel? +

ibkr_global_cancel is provided by the Ibkr MCP server (patrickpxp/ibkr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ibkr tool call.

Start from Ibkr, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

33 Ibkr tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.