This record as markdown: /tools/aapanel-mcp/task-remove.md
What task_remove does on Aapanel
AI agents call task_remove to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why task_remove is rated Critical
Removing or canceling a background task is an irreversible action that stops ongoing operations and cannot be easily undone. This differs from a Write operation (which modifies data reversibly) because task termination is destructive—the task state cannot be restored without manual intervention or re-initialization.
From the tool's definition Tool name 'task_remove' with description 'Remove/cancel a background task' indicates irreversible deletion or termination of an active process/task.
Attacks that exploit this kind of access
The rule that runs task_remove safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For task_remove, this is the rule to start with:
task_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every task_remove call is checked against it from then on.
Questions about task_remove
Remove/cancel a background task. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for task_remove: 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 Aapanel. Nothing to install.
task_remove 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 task_remove 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 task_remove. 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.
task_remove is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue