Low Risk

fetch_trades

Fetch the history of closed trades. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with trade history, or None if failed.

How to control fetch_trades ↓

What fetch_trades does on Freqtrade

AI agents call fetch_trades to retrieve information from Freqtrade without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why fetch_trades needs a policy

This tool retrieves historical trading data for querying and analysis purposes. It performs a read-only operation on past trade records with no ability to modify, delete, or execute trades. The blast radius of misuse is minimal—an agent could view trade history but cannot alter balances, execute new trades, or cause financial harm through this tool alone.

From the tool's definition Tool name is 'fetch_trades' and description states it 'Fetch the history of closed trades' with no modification or execution capability. It returns trade history data with no side effects.

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

How to control fetch_trades

PolicyLayer is an MCP gateway — it sits between your AI agents and Freqtrade, and nothing reaches the server without passing your rules. This is the rule we recommend for fetch_trades:

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

fetch_trades 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 Freqtrade — 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_trades

What does the fetch_trades tool do? +

Fetch the history of closed trades. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response with trade history, or None if failed. It is categorised as a Read tool in the Freqtrade MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_trades? +

Register the Freqtrade MCP server in PolicyLayer and add a rule for fetch_trades: 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 Freqtrade. Nothing to install.

What risk level is fetch_trades? +

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

Can I rate-limit fetch_trades? +

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

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

fetch_trades is provided by the Freqtrade MCP server (kukapay/freqtrade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Freqtrade tool call.

Start from Freqtrade, 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.

17 Freqtrade 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.