AI agents invoke stop_bot to trigger actions in Crypto Multi-MCP Hub. 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.
Although 'stop_bot' itself is not destructive (it does not delete data or cancel trades), it executes a control operation that halts an autonomous system. Given the crypto trading context with active order creation and execution, stopping a bot mid-operation could have significant financial consequences depending on the bot's state and outstanding positions.
From the tool's definition Tool name 'stop_bot' indicates termination of an autonomous trading bot. Context shows this server executes 'autonomous trading agent execution' with sibling tools including 'create_order', 'cancel_order', and 'execute_approved_order' that manipulate…
Documented attack patterns abuse exactly the kind of access stop_bot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Multi-MCP Hub, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_bot:
{
"version": "1",
"default": "deny",
"tools": {
"stop_bot": {
"limits": [
{
"counter": "stop_bot_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
stop_bot. It is categorised as a Execute tool in the Crypto Multi-MCP Hub MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crypto Multi-MCP Hub 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 Crypto Multi-MCP Hub. Nothing to install.
stop_bot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
stop_bot is provided by the Crypto Multi-MCP Hub MCP server (pellenybe/crypto-mcp-server---by-corax-colab). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Multi-MCP Hub, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Crypto Multi-MCP Hub tools catalogued and risk-classified — across an index of 43,000+ MCP servers.