ccxt_transfer
Call exchange.transfer(code, amount, fromAccount, toAccount, params), subject to the trading gate.
This record as markdown: /tools/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-transfer.md
What ccxt_transfer does on Codex CCXT MCP
AI agents use ccxt_transfer 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_transfer is rated Critical
The transfer function moves money or assets between accounts on a cryptocurrency exchange. This is a core Financial operation that can irreversibly commit funds. Even with dry-run-first safeguards mentioned in the server description and a trading gate, the tool's primary action is to execute financial transfers.
From the tool's definition Tool performs 'transfer(code, amount, fromAccount, toAccount)' — explicitly moves currency (code) and amount between accounts, a direct financial operation that commits obligations and moves value.
Attacks that exploit this kind of access
The rule that runs ccxt_transfer 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_transfer, this is the rule to start with:
Any call to ccxt_transfer 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_transfer call is checked against it from then on.
Questions about ccxt_transfer
Call exchange.transfer(code, amount, fromAccount, toAccount, 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_transfer: 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_transfer 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_transfer 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_transfer. 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_transfer 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