fetch_backtest_status

Get current backtest execution status and latest result payload.

Server Freqtrade-MCP worlddebugger/freqtrade-mcp
Category Read
Risk class Low
Parameters 00 required

What fetch_backtest_status does on Freqtrade-MCP

AI agents call fetch_backtest_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.

Why fetch_backtest_status needs a policy

This tool only retrieves information about backtest execution status and results. It performs no side effects, makes no modifications to data, executes no code, and creates no financial transactions. It is a straightforward read operation consistent with monitoring and observability tasks. The low severity reflects minimal blast radius—misuse would only expose information already available to an authenticated user.

From the tool's definition Tool name 'fetch_backtest_status' and description 'Get current backtest execution status and latest result payload' indicate a retrieval operation that queries the status of a backtest and returns results without modifying any data.

Questions about fetch_backtest_status

What does the fetch_backtest_status tool do? +

Get current backtest execution status and latest result payload. It is categorised as a Read tool in the Freqtrade-MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_backtest_status? +

Register the Freqtrade- MCP server in PolicyLayer and add a rule for fetch_backtest_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.

What risk level is fetch_backtest_status? +

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

Can I rate-limit fetch_backtest_status? +

Yes. Add a rate_limit block to the fetch_backtest_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.

How do I block fetch_backtest_status completely? +

Set action: deny in the PolicyLayer policy for fetch_backtest_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.

What MCP server provides fetch_backtest_status? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.