AI agents call fetchDeposits 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 queries and returns historical deposit transaction data from a cryptocurrency exchange account. While it is a Read operation (no data modification), the severity is elevated to medium because deposit history can reveal sensitive financial information including transaction patterns, timing, amounts, and wallet addresses associated with the account.
From the tool's definition 'fetchDeposits' retrieves deposit history for a configured account. The verb 'fetch' and function name indicate data retrieval without modification. The description explicitly states it retrieves historical data with no side effects.
Documented attack patterns abuse exactly the kind of access fetchDeposits 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 fetchDeposits:
{
"version": "1",
"default": "deny",
"tools": {
"fetchDeposits": {}
}
}fetchDeposits 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 deposit 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 fetchDeposits: 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.
fetchDeposits 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 fetchDeposits 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 fetchDeposits. 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.
fetchDeposits 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.