run_backtest · Freqtrade- MCP: Risk & Policy

WHAT IT DOES

What run_backtest does on Freqtrade-MCP

AI agents invoke run_backtest to trigger actions in Freqtrade-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_backtest needs a policy

This tool triggers execution of a backtesting operation on a trading bot system. While a backtest itself is a simulation and not a live trade, it is an Execute action because it runs code/operations whose effects depend on the arguments provided (backtest parameters, strategy, data range).

From the tool's definition The tool 'run_backtest' starts a REST backtest job. The verb 'run' combined with 'backtest' indicates execution of a computational operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_backtest Rate-limited

run_backtest stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_backtest": {
      "limits": [
        {
          "counter": "run_backtest_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Freqtrade-MCP, so you can run agents against it safely.

FAQ

Questions about run_backtest

What does the run_backtest tool do? +

Start a REST backtest job. It is categorised as a Execute tool in the Freqtrade-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_backtest? +

Register the Freqtrade- MCP server in PolicyLayer and add a rule for run_backtest: 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 run_backtest? +

run_backtest is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_backtest? +

Yes. Add a rate_limit block to the run_backtest 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 run_backtest completely? +

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

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