cancelSpreadOrder
Cancel a single spread trading order by its order ID or custom order link ID.\n\nUsage Scenarios:\n- Cancel an open limit order that has not yet been fully filled.\n- Use either
This record as markdown: /tools/bybit-exchange-trading-mcp/cancelspreadorder.md
What cancelSpreadOrder does on Bybit MCP Server
AI agents call cancelSpreadOrder to permanently remove resources in Bybit MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancelSpreadOrder is rated Critical
Cancelling a trading order is an irreversible action — once cancelled, the order cannot be reinstated. This affects live trading operations on a cryptocurrency exchange, and misuse could disrupt trading strategies or cause financial harm by removing open orders at critical market moments. While not directly moving money, it irreversibly terminates an order, classifying it as Destructive with high severity.
From the tool's definition Cancel a single spread trading order by its order ID or custom order link ID. Cancel an open limit order that has not yet been fully filled.
Attacks that exploit this kind of access
The rule that runs cancelSpreadOrder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancelSpreadOrder, this is the rule to start with:
cancelSpreadOrder is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every cancelSpreadOrder call is checked against it from then on.
Questions about cancelSpreadOrder
Cancel a single spread trading order by its order ID or custom order link ID.\n\nUsage Scenarios:\n- Cancel an open limit order that has not yet been fully filled.\n- Use either. It is categorised as a Destructive tool in the Bybit MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for cancelSpreadOrder: 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 Bybit MCP Server. Nothing to install.
cancelSpreadOrder 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 cancelSpreadOrder 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 cancelSpreadOrder. 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.
cancelSpreadOrder is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit MCP Server, and thousands of servers like it.
Across the catalogue