Low Risk

fetch_market_data

fetch_market_data

How to control fetch_market_data ↓

What fetch_market_data does on Freqtrade

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

The 'fetch_' prefix strongly suggests this tool retrieves market data without modifying state. Market data retrieval is a non-destructive read operation. Confidence is moderate (0.7) rather than high due to the empty description; however, the naming convention and context of sibling tools provide strong contextual evidence. No write, delete, execute, or financial transaction capability is indicated.

From the tool's definition Tool name 'fetch_market_data' indicates data retrieval. Description is empty, but naming pattern is consistent with other sibling tools on this server that use 'fetch_' prefix (fetch_balance, fetch_blacklist, fetch_bot_status, fetch_config, fetch_locks,…

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

How to control fetch_market_data

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

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

fetch_market_data 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_market_data

What does the fetch_market_data tool do? +

fetch_market_data. 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_market_data? +

Register the Freqtrade MCP server in PolicyLayer and add a rule for fetch_market_data: 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_market_data? +

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

Can I rate-limit fetch_market_data? +

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

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

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