stop_bot

Deactivate (stop) a strategy/bot. The bot stops opening new deals but keeps existing ones open.

SERVER:GT Protocol MCP Server SOURCEgt-protocol/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gt-protocol-mcp/stop-bot.md

WHAT IT DOES

What stop_bot does on :GT Protocol MCP Server

AI agents invoke stop_bot to trigger actions in :GT Protocol MCP Server. 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.

RISK

Why stop_bot is rated High

While the tool doesn't execute a direct financial transaction (Financial) or permanently delete data (Destructive), it modifies the operational state of an automated trading system. The ability to stop/start bots affects active deal management and trading strategy execution on live trading accounts.

From the tool's definition Deactivates an automated trading bot on financial exchanges (Binance, Hyperliquid). The description states it 'stops opening new deals but keeps existing ones open,' indicating active control of a trading system whose state changes have real financial…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_bot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and :GT Protocol MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_bot, this is the rule to start with:

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.

The button opens the PolicyLayer dashboard: create your workspace, connect :GT Protocol MCP Server, apply this rule, and every stop_bot call is checked against it from then on.

FAQ

Questions about stop_bot

What does the stop_bot tool do? +

Deactivate (stop) a strategy/bot. The bot stops opening new deals but keeps existing ones open. It is categorised as a Execute tool in the :GT Protocol MCP Server 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 :GT Protocol MCP Server 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 :GT Protocol MCP Server. 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 :GT Protocol MCP Server MCP server (gt-protocol/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on :GT Protocol MCP Server, and thousands of servers like it.

This server

All 19 :GT Protocol MCP Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →