ccxt_create_stop_loss_order
Call exchange.createStopLossOrder(symbol, type, side, amount, price, stopLossPrice, params), subject to the trading gate.
This record as markdown: /tools/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-create-stop-loss-order.md
What ccxt_create_stop_loss_order does on Codex CCXT MCP
AI agents use ccxt_create_stop_loss_order to commit financial operations through Codex CCXT MCP, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why ccxt_create_stop_loss_order is rated Critical
This tool places a stop-loss order on a financial exchange, which commits a financial obligation to sell/buy an asset when a trigger price is reached. Even with a 'trading gate' guard, misuse or unintended triggering could result in real trades executing and moving money. This falls squarely in the Financial category with critical severity due to potential for significant financial loss if misused by an AI agent.
From the tool's definition createStopLossOrder(symbol, type, side, amount, price, stopLossPrice, params), subject to the trading gate
Attacks that exploit this kind of access
The rule that runs ccxt_create_stop_loss_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_create_stop_loss_order, this is the rule to start with:
Any call to ccxt_create_stop_loss_order is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Codex CCXT MCP, apply this rule, and every ccxt_create_stop_loss_order call is checked against it from then on.
Questions about ccxt_create_stop_loss_order
Call exchange.createStopLossOrder(symbol, type, side, amount, price, stopLossPrice, params), subject to the trading gate. It is categorised as a Financial tool in the Codex CCXT MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_create_stop_loss_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_create_stop_loss_order is a Financial 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 ccxt_create_stop_loss_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_create_stop_loss_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_create_stop_loss_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