This record as markdown: /tools/johnnywic-bybit-mcp/cancel-spread-order.md
What cancel_spread_order does on Bybit
AI agents call cancel_spread_order to permanently remove resources in Bybit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_spread_order is rated Critical
Canceling a spread trading order on Bybit is an irreversible operation that terminates a financial commitment. While the cancellation itself is a standard order management operation, it cannot be undone once executed—the order is permanently removed from the order book. This fits the Destructive category (irreversible deletion of data/state).
From the tool's definition cancel_spread_order: Cancel a spread trading order. The tool irreversibly cancels an existing order on a financial exchange, removing its effect and preventing its execution.
Attacks that exploit this kind of access
The rule that runs cancel_spread_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_spread_order, this is the rule to start with:
cancel_spread_order 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, apply this rule, and every cancel_spread_order call is checked against it from then on.
Questions about cancel_spread_order
Cancel a spread trading order. It is categorised as a Destructive tool in the Bybit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bybit MCP server in PolicyLayer and add a rule for cancel_spread_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 Bybit. Nothing to install.
cancel_spread_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_spread_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_spread_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_spread_order is provided by the Bybit MCP server (johnnywic/bybit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Bybit, and thousands of servers like it.
Across the catalogue