Delete a working order
AI agents call ig_delete_working_order to permanently remove resources in IG Trading MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a working order is an irreversible action that removes a pending trade instruction from the system. While not a direct financial transaction, it destroys order state and cannot be recovered, making it destructive rather than write. In a trading context, unintended deletion of orders could cause significant financial harm by preventing intended trades or exposing positions.
From the tool's definition Tool name 'ig_delete_working_order' and description 'Delete a working order' indicate irreversible deletion of a financial order. This is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
Delete a working order. It is categorised as a Destructive tool in the IG Trading MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IG Trading MCP server in PolicyLayer and add a rule for ig_delete_working_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 IG Trading MCP. Nothing to install.
ig_delete_working_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 ig_delete_working_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 ig_delete_working_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.
ig_delete_working_order is provided by the IG Trading MCP server (kea0811/ig-trading-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 →