Retrieve the current bot configuration.
AI agents call fetch_config 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 configuration data from the Freqtrade trading bot. While it is a Read operation (no data modification), the severity is elevated to 'medium' because bot configuration often contains sensitive information such as API keys, exchange credentials, wallet addresses, trading pairs, risk parameters, and other security-critical settings.
From the tool's definition Tool name is 'fetch_config' with description 'Retrieve the current bot configuration.' The verb 'Retrieve' and 'fetch' indicate a read-only data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Retrieve the current bot configuration. 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_config: 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_config 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_config 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_config. 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_config 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 →