fetchMyTrades

THE RISK

Low Risk

Why fetchMyTrades needs a policy

This tool retrieves existing trade history data without modifying, executing operations, or committing financial transactions. It is a query operation similar to other Read-category tools like 'fetchBalance', 'fetchClosedOrders', and 'fetchDeposits' on the same server.

From the tool's definition Tool name 'fetchMyTrades' and description 'Fetch personal trade history for a configured account' indicate a retrieval operation with no side effects. The verb 'fetch' and context of querying historical data confirm read-only semantics.

Documented attack patterns abuse exactly the kind of access fetchMyTrades gives an agent:

POLICY

How to control fetchMyTrades

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 fetchMyTrades:

policy.json

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

fetchMyTrades is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register CCXT MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CCXT MCP Server tools

Financial createOrder Create a new order using a configured account Destructive cancelOrder Cancel an existing order using a configured account Read analyzeConsecutiveProfitLoss Analyze consecutive winning and losing trades Read analyzePeriodicReturns Analyze daily and monthly returns for a configured account Read analyzeTradingPerformance Analyze trading performance for a configured account Read calculateWinRate Calculate win rate and profit metrics for a configured account Read fetchBalance Fetch account balance for a configured account Read fetchClosedOrders Fetch all closed orders using a configured account

All 20 CCXT MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fetchMyTrades

What does the fetchMyTrades tool do? +

Fetch personal trade 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.

How do I enforce a policy on fetchMyTrades? +

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

What risk level is fetchMyTrades? +

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

Can I rate-limit fetchMyTrades? +

Yes. Add a rate_limit block to the fetchMyTrades 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 fetchMyTrades completely? +

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

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

Enforce policy on every CCXT MCP Server tool call.

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.

CHECK YOUR STACK →