ccxt_fetch_deposits_withdrawals
Call exchange.fetchDepositsWithdrawals(code, since, limit, params).
This record as markdown: /tools/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-fetch-deposits-withdrawals.md
What ccxt_fetch_deposits_withdrawals does on Codex CCXT MCP
AI agents call ccxt_fetch_deposits_withdrawals to retrieve information from Codex CCXT MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ccxt_fetch_deposits_withdrawals is rated Low
This tool retrieves historical account transaction data (deposits and withdrawals) from an exchange. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute any transactions. The 'fetch' verb and the data retrieval nature of fetchDepositsWithdrawals() confirm this is a Read category tool.
From the tool's definition Tool name contains 'fetch' and description indicates it calls exchange.fetchDepositsWithdrawals(), which queries historical deposit and withdrawal transaction data without modifying or executing external operations.
Attacks that exploit this kind of access
The rule that runs ccxt_fetch_deposits_withdrawals 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_fetch_deposits_withdrawals, this is the rule to start with:
ccxt_fetch_deposits_withdrawals is read-only, so it stays allowed. 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_fetch_deposits_withdrawals call is checked against it from then on.
Questions about ccxt_fetch_deposits_withdrawals
Call exchange.fetchDepositsWithdrawals(code, since, limit, params). It is categorised as a Read tool in the Codex CCXT MCP MCP Server, which means it retrieves data without modifying state.
Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_fetch_deposits_withdrawals: 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_fetch_deposits_withdrawals is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ccxt_fetch_deposits_withdrawals 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_fetch_deposits_withdrawals. 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_fetch_deposits_withdrawals 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.
This server
Across the catalogue