New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cancel_spread_order

Cancel a spread trading order.

SERVERBybit SOURCEjohnnywic/bybit-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about cancel_spread_order

What does the cancel_spread_order tool do? +

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.

How do I enforce a policy on cancel_spread_order? +

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.

What risk level is cancel_spread_order? +

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.

Can I rate-limit cancel_spread_order? +

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.

How do I block cancel_spread_order completely? +

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.

What MCP server provides cancel_spread_order? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Bybit's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.