Retrieve the current status of open trades.
AI agents call fetch_bot_status 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.
This tool retrieves status information about open trades—a pure data query with no capability to modify state, execute trades, delete data, or commit financial transactions. The use of 'fetch' and 'retrieve' confirms read semantics. Severity is low because querying trade status poses minimal risk even if misused by an AI agent; it cannot alter positions or commit funds.
From the tool's definition Tool name 'fetch_bot_status' and description 'Retrieve the current status of open trades' indicate a read-only operation that queries data without modification or side effects.
Attacks that exploit this kind of access
Retrieve the current status of open trades. 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_bot_status: 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_bot_status 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_bot_status 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_bot_status. 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_bot_status 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 →