ccxt_fetch_positions_history

Call exchange.fetchPositionsHistory(symbols, 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-positions-history.md

WHAT IT DOES

What ccxt_fetch_positions_history does on Codex CCXT MCP

AI agents call ccxt_fetch_positions_history 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_positions_history is rated Low

This tool retrieves historical trading positions from the exchange. The 'fetch' prefix indicates a read-only query operation with no side effects. Even though it operates on a trading/financial context, it neither moves money, executes trades, nor modifies data - it only queries existing position history.

From the tool's definition Tool name contains 'fetch' and description shows 'fetchPositionsHistory' - a query method that retrieves historical position data without modifying state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ccxt_fetch_positions_history Allowed

ccxt_fetch_positions_history 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_positions_history": {}
  }
}

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_positions_history call is checked against it from then on.

FAQ

Questions about ccxt_fetch_positions_history

What does the ccxt_fetch_positions_history tool do? +

Call exchange.fetchPositionsHistory(symbols, 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_positions_history? +

Register the Codex CCXT MCP server in PolicyLayer and add a rule for ccxt_fetch_positions_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 Codex CCXT MCP. Nothing to install.

What risk level is ccxt_fetch_positions_history? +

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

Can I rate-limit ccxt_fetch_positions_history? +

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

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

ccxt_fetch_positions_history 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 →