ccxt_cancel_order
Call exchange.cancelOrder(id, symbol, params), subject to the trading gate.
This record as markdown: /tools/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-cancel-order.md
What ccxt_cancel_order does on Codex CCXT MCP
AI agents invoke ccxt_cancel_order to trigger actions in Codex CCXT MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why ccxt_cancel_order is rated High
Cancelling an order triggers an external operation on the exchange that terminates an active order. While it doesn't move money directly, it is an irreversible action affecting live trading state on an external system. It is gated by a trading gate (dry-run guard), indicating real financial side effects are possible.
From the tool's definition Call exchange.cancelOrder(id, symbol, params), subject to the trading gate.
Attacks that exploit this kind of access
The rule that runs ccxt_cancel_order safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Codex CCXT MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ccxt_cancel_order, this is the rule to start with:
ccxt_cancel_order stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Codex CCXT MCP, apply this rule, and every ccxt_cancel_order call is checked against it from then on.
Questions about ccxt_cancel_order
Call exchange.cancelOrder(id, symbol, params), subject to the trading gate. It is categorised as a Execute tool in the Codex CCXT MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_cancel_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.
ccxt_cancel_order is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ccxt_cancel_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 ccxt_cancel_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.
ccxt_cancel_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.
Across the catalogue