Get profit summary for the trading bot.
AI agents call fetch_profit 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 profit summary data from the Freqtrade bot without creating, modifying, deleting, or executing any operations. It is a passive query operation that only reads existing trading performance metrics. While the underlying server manages cryptocurrency trading (financial domain), this specific tool does not move money, execute trades, or make financial commitments—it merely reports on existing results.
From the tool's definition Tool name 'fetch_profit' and description 'Get profit summary for the trading bot' indicate a data retrieval operation with no side effects. The verb 'fetch' and 'get' are characteristic of Read category tools.
Attacks that exploit this kind of access
Get profit summary for the trading bot. 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_profit: 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_profit 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_profit 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_profit. 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_profit 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 →