Low Risk

fetchClosedOrders

Fetch all closed orders using a configured account

How to control fetchClosedOrders ↓

What fetchClosedOrders does on CCXT MCP Server

AI agents call fetchClosedOrders 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 fetchClosedOrders needs a policy

This tool retrieves historical order data from a cryptocurrency exchange. It queries past trading activity without creating, modifying, deleting, or executing any new orders or transactions. While the CCXT server provides access to trading capabilities, this specific tool is strictly informational and read-only, presenting minimal security risk beyond potential information disclosure.

From the tool's definition Tool name 'fetchClosedOrders' and description 'Fetch all closed orders using a configured account' indicate data retrieval with no modification or execution. The verb 'fetch' is characteristic of read-only operations.

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

How to control fetchClosedOrders

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

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

fetchClosedOrders 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 fetchClosedOrders

What does the fetchClosedOrders tool do? +

Fetch all closed orders using 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 fetchClosedOrders? +

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

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

Can I rate-limit fetchClosedOrders? +

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

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

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

Free to start. No card required.

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