// MCP TOOL REFERENCE

reload_config

Reload the bot configuration. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response or success message, or error if failed.

ServerFreqtrade
CategoryExecute

How to control reload_config ↓

WHAT IT DOES

What reload_config does on Freqtrade

AI agents invoke reload_config to trigger actions in Freqtrade. 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.

THE RISK

High Risk

Why reload_config needs a policy

Reloading the bot configuration triggers an operational action on the trading bot — it causes the bot to re-read and apply its configuration, which can change trading behavior (pairs, strategies, risk parameters, etc.). This is not a simple read, nor does it delete data, but it executes an operational command with potentially significant side effects on a live trading system.

From the tool's definition Reload the bot configuration

Documented attack patterns abuse exactly the kind of access reload_config gives an agent:

POLICY

How to control reload_config

PolicyLayer is an MCP gateway — it sits between your AI agents and Freqtrade, and nothing reaches the server without passing your rules. This is the rule we recommend for reload_config:

policy.json

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

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.

Create a free account and register Freqtrade — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Freqtrade tools

Financial place_trade place_trade Destructive delete_blacklist delete_blacklist Destructive delete_lock Delete a specific trade lock by ID. Parameters: lock_id (int): ID of the Execute start_bot Start the Freqtrade bot. Parameters: ctx (Context): MCP context object fo Execute stop_bot Stop the Freqtrade bot. Parameters: ctx (Context): MCP context object for Write add_blacklist add_blacklist Read fetch_balance Fetch the account balance. Parameters: ctx (Context): MCP context object Read fetch_blacklist Get the current blacklist of trading pairs. Parameters: ctx (Context): MC

All 17 Freqtrade tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Freqtrade → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reload_config

What does the reload_config tool do? +

Reload the bot configuration. Parameters: ctx (Context): MCP context object for logging and client access. Returns: str: Stringified JSON response or success message, or error if failed. It is categorised as a Execute tool in the Freqtrade 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. 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 (kukapay/freqtrade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Freqtrade tool call.

Start from Freqtrade, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

17 Freqtrade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.