reload_config · Freqtrade- MCP: Risk & Policy

WHAT IT DOES

What reload_config does on Freqtrade-MCP

AI agents invoke reload_config 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 reload_config needs a policy

Reloading the bot configuration is an external operation that causes the running trading bot to reinitialize with potentially new settings. It is not purely a read (it changes bot state) nor a write (it doesn't persist new data), but rather executes a runtime action. Misuse could disrupt active trades or change trading parameters unexpectedly, warranting medium severity.

From the tool's definition 'Reload the bot configuration' — triggers an operational action on the trading bot that restarts/reapplies configuration, affecting live trading behavior

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_config Rate-limited

reload_config 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": {
    "reload_config": {
      "limits": [
        {
          "counter": "reload_config_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 reload_config

What does the reload_config tool do? +

Reload the bot configuration. 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 reload_config? +

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

What risk level is reload_config? +

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

Can I rate-limit reload_config? +

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

How do I block reload_config completely? +

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

What MCP server provides reload_config? +

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