AI agents call cancel_task to permanently remove resources in Hive — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a task is irreversible — the task's in-progress computation is terminated and cannot be resumed. Any partial results are lost. This is a destructive action (though limited in blast radius since no persistent data is deleted, just the running work unit), making Destructive the most appropriate category over Execute or Write.
From the tool's definition Cancel a pending or running task
Documented attack patterns abuse exactly the kind of access cancel_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hive, and nothing reaches the server without passing your rules. This is the rule we recommend for cancel_task:
{
"version": "1",
"default": "deny",
"hide": [
"cancel_task"
]
}cancel_task disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Cancel a pending or running task. It is categorised as a Destructive tool in the Hive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hive MCP server in PolicyLayer and add a rule for cancel_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 Hive. Nothing to install.
cancel_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_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 cancel_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.
cancel_task is provided by the Hive MCP server (saikodi/hive-compute-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hive, 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.
12 Hive tools catalogued and risk-classified — across an index of 43,000+ MCP servers.