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

pause_background_task

A execute tool on the Allcanuse MCP server.

SERVERAllcanuse SOURCEra1nyxin/allcanuse-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/ra1nyxin-allcanuse-mcp/pause-background-task.md

What pause_background_task does on Allcanuse

AI agents invoke pause_background_task to trigger actions in Allcanuse. 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.

Why pause_background_task is rated High

The tool likely pauses a running background task, which is an execution control operation. The description is empty, reducing confidence. Based on naming convention and sibling tools (create/cancel background tasks), this tool controls execution state of running processes. Severity is medium as pausing tasks can disrupt system operations but is generally reversible.

From the tool's definition Tool name 'pause_background_task' and sibling tools like 'create_background_task', 'cancel_background_task' suggest managing background task execution lifecycle.

Questions about pause_background_task

What does the pause_background_task tool do? +

pause_background_task is a execute tool on the Allcanuse MCP server. It is categorised as a Execute tool in the Allcanuse MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pause_background_task? +

Register the Allcanuse MCP server in PolicyLayer and add a rule for pause_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 pause_background_task? +

pause_background_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pause_background_task? +

Yes. Add a rate_limit block to the pause_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 pause_background_task completely? +

Set action: deny in the PolicyLayer policy for pause_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 pause_background_task? +

pause_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.