AI agents invoke stop_task 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.
Without description, confidence is moderate (0.7). However, in a crypto trading context with autonomous agents and active orders (create_order, cancel_order, execute_approved_order present), stopping a task could halt critical operations mid-execution, causing incomplete trades or loss of state.
From the tool's definition Tool name 'stop_task' with empty description. Given the server context (autonomous trading agent execution, order management, crypto operations), this tool likely terminates running processes or agents.
Documented attack patterns abuse exactly the kind of access stop_task 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_task:
{
"version": "1",
"default": "deny",
"tools": {
"stop_task": {
"limits": [
{
"counter": "stop_task_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_task 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_task. 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_task: 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_task 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_task 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_task. 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_task 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.