ccxt_cancel_algo_order

Call Binance Futures fapiPrivateDeleteAlgoOrder(params) for conditional protection orders.

SERVERCodex CCXT MCP SOURCEoci:ghcr.io/lucyfox199818-collab/ccxt-mcp:0.1.0
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/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-cancel-algo-order.md

What ccxt_cancel_algo_order does on Codex CCXT MCP

AI agents call ccxt_cancel_algo_order to permanently remove resources in Codex CCXT MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why ccxt_cancel_algo_order is rated Critical

This tool cancels (deletes) an existing algorithmic/conditional order on Binance Futures. Cancelling an active protection order (e.g., stop-loss, take-profit) is irreversible in the sense that the protective hedge is removed and cannot be automatically reinstated.

From the tool's definition cancel_algo_order... fapiPrivateDeleteAlgoOrder(params) for conditional protection orders

Questions about ccxt_cancel_algo_order

What does the ccxt_cancel_algo_order tool do? +

Call Binance Futures fapiPrivateDeleteAlgoOrder(params) for conditional protection orders. It is categorised as a Destructive tool in the Codex CCXT MCP 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 ccxt_cancel_algo_order? +

Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_cancel_algo_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 Codex CCXT MCP. Nothing to install.

What risk level is ccxt_cancel_algo_order? +

ccxt_cancel_algo_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 ccxt_cancel_algo_order? +

Yes. Add a rate_limit block to the ccxt_cancel_algo_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 ccxt_cancel_algo_order completely? +

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

ccxt_cancel_algo_order is provided by the Codex CCXT MCP server (oci:ghcr.io/lucyfox199818-collab/ccxt-mcp:0.1.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Codex CCXT, 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 Codex CCXT'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.