Low Risk

fetch_my_trade_history

Fetches the history of your executed trades (fills) for an account, optionally filtered by symbol, time, and limit.

How to control fetch_my_trade_history ↓

What fetch_my_trade_history does on CCXT MCP Server

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

Low Risk

Why fetch_my_trade_history needs a policy

This tool retrieves historical trade data from an account without modifying, deleting, or executing any trades. It is a query operation that returns information already in the system. While the data retrieved is financially sensitive (trade history), the tool itself performs no financial transactions, modifications, or irreversible operations.

From the tool's definition Tool name 'fetch_my_trade_history' and description 'Fetches the history of your executed trades' indicate a retrieval operation with no side effects.

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

How to control fetch_my_trade_history

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_my_trade_history": {}
  }
}

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

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about fetch_my_trade_history

What does the fetch_my_trade_history tool do? +

Fetches the history of your executed trades (fills) for an account, optionally filtered by symbol, time, and limit. 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 fetch_my_trade_history? +

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

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

Can I rate-limit fetch_my_trade_history? +

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

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

fetch_my_trade_history is provided by the CCXT MCP Server MCP server (jcwleo/ccxt-mcp-server). 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.

Free to start. No card required.

19 CCXT MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.