fetch_market_data
AI agents call fetch_market_data to retrieve information from Freqtrade-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Fetching market data is a read-only operation that retrieves information without side effects. Even in a financial/trading context, querying market data poses minimal risk—it neither executes trades, deletes data, nor moves funds. The blast radius of misuse is low (an agent might fetch unnecessary data but cannot cause financial loss or irreversible damage via this tool alone).
From the tool's definition Tool name 'fetch_market_data' indicates retrieval of market data with no modification. Server context confirms it 'fetch[es] market data' as a read operation alongside other fetch_* tools (fetch_balance, fetch_backtest_history, fetch_bot_status).
Attacks that exploit this kind of access
fetch_market_data. It is categorised as a Read tool in the Freqtrade-MCP MCP Server, which means it retrieves data without modifying state.
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-MCP. Nothing to install.
fetch_market_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
fetch_market_data is provided by the Freqtrade- MCP server (worlddebugger/freqtrade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →