New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cancel_background_task

A destructive tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ra1nyxin-allcanuse-mcp/cancel-background-task.md

What cancel_background_task does on Allcanuse

AI agents call cancel_background_task to permanently remove resources in Allcanuse, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why cancel_background_task is rated Critical

The name 'cancel_background_task' implies terminating/stopping a background task that was previously created. Cancellation of a running task is typically irreversible (the task's progress may be lost), placing it in the Destructive category. However, the empty description lowers confidence significantly — it could be a softer 'pause' or reversible stop.

From the tool's definition Tool name: cancel_background_task; description is empty

Questions about cancel_background_task

What does the cancel_background_task tool do? +

cancel_background_task is a destructive tool on the Allcanuse MCP server. It is categorised as a Destructive tool in the Allcanuse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on cancel_background_task? +

Register the Allcanuse MCP server in PolicyLayer and add a rule for cancel_background_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 Allcanuse. Nothing to install.

What risk level is cancel_background_task? +

cancel_background_task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit cancel_background_task? +

Yes. Add a rate_limit block to the cancel_background_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.

How do I block cancel_background_task completely? +

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

What MCP server provides cancel_background_task? +

cancel_background_task is provided by the Allcanuse MCP server (ra1nyxin/allcanuse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Allcanuse, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Allcanuse's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.