Fetch withdrawal history for a configured account
AI agents call fetchWithdrawals to retrieve information from CCXT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves past withdrawal records from an exchange account. It is a read-only query operation that does not create, modify, delete, or execute any actions. While it accesses financial account data (which exists on a cryptocurrency exchange), the tool itself merely queries historical information without moving money or committing financial obligations.
From the tool's definition Tool name is 'fetchWithdrawals' and description states 'Fetch withdrawal history for a configured account'. The verb 'fetch' combined with 'history' indicates retrieval of historical data with no side effects.
Documented attack patterns abuse exactly the kind of access fetchWithdrawals gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CCXT MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for fetchWithdrawals:
{
"version": "1",
"default": "deny",
"tools": {
"fetchWithdrawals": {}
}
} fetchWithdrawals is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch withdrawal history for a configured account. It is categorised as a Read tool in the CCXT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CCXT MCP Server MCP server in PolicyLayer and add a rule for fetchWithdrawals: 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 CCXT MCP Server. Nothing to install.
fetchWithdrawals 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 fetchWithdrawals 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 fetchWithdrawals. 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.
fetchWithdrawals is provided by the CCXT MCP Server MCP server (lazy-dinosaur/ccxt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CCXT MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 CCXT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.