stop_bot · Freqtrade- MCP: Risk & Policy

WHAT IT DOES

What stop_bot does on Freqtrade-MCP

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

This tool executes a command to stop an active cryptocurrency trading bot. While it does not delete data (not Destructive) or move money directly (not Financial), it is an Execute category tool because it triggers an external operation whose effects depend on context—stopping a bot actively managing trades can have significant financial consequences by interrupting ongoing trading operations.

From the tool's definition Tool description: 'Stop the Freqtrade bot.' This directly triggers an external operation (halting bot execution) whose effects are immediate and depend on the bot's current state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_bot Rate-limited

stop_bot 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": {
    "stop_bot": {
      "limits": [
        {
          "counter": "stop_bot_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 stop_bot

What does the stop_bot tool do? +

Stop the Freqtrade bot. 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 stop_bot? +

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

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

Can I rate-limit stop_bot? +

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

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

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