ccxt_fetch_deposits

Call exchange.fetchDeposits(code, since, limit, params).

SERVERCodex CCXT MCP SOURCEoci:ghcr.io/lucyfox199818-collab/ccxt-mcp:0.1.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-lucyfox199818-collab-ccxt-mcp/ccxt-fetch-deposits.md

WHAT IT DOES

What ccxt_fetch_deposits does on Codex CCXT MCP

AI agents call ccxt_fetch_deposits 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.

RISK

Why ccxt_fetch_deposits is rated Low

This tool queries and retrieves historical deposit records from an exchange account. It performs no writes, deletions, code execution, or financial transactions. The parameters (code, since, limit, params) are all filtering/querying options with no destructive capability. The read-only nature and lack of side effects place it squarely in the Read category with low severity.

From the tool's definition Tool name includes 'fetch' and description uses 'fetchDeposits()' which retrieves deposit history data without modifying account state or executing transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ccxt_fetch_deposits 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, this is the rule to start with:

ccxt_fetch_deposits Allowed

ccxt_fetch_deposits is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ccxt_fetch_deposits": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Codex CCXT MCP, apply this rule, and every ccxt_fetch_deposits call is checked against it from then on.

FAQ

Questions about ccxt_fetch_deposits

What does the ccxt_fetch_deposits tool do? +

Call exchange.fetchDeposits(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.

How do I enforce a policy on ccxt_fetch_deposits? +

Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_fetch_deposits: 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.

What risk level is ccxt_fetch_deposits? +

ccxt_fetch_deposits is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ccxt_fetch_deposits? +

Yes. Add a rate_limit block to the ccxt_fetch_deposits 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.

How do I block ccxt_fetch_deposits completely? +

Set action: deny in the PolicyLayer policy for ccxt_fetch_deposits. 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.

What MCP server provides ccxt_fetch_deposits? +

ccxt_fetch_deposits 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.

KEEP EXPLORING

More on Codex CCXT, and thousands of servers like it.

This server

All 113 Codex CCXT tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →