Remove multiple tasks from the active checklist. Safe for batch deletion, as remaining tasks are dynamically re-indexed only after all specified removals are processed.
AI agents call remove_tasks to permanently remove resources in Subconductor — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes task records from the checklist without the ability to undo or recover them. While the description emphasizes it is 'safe for batch deletion', the core operation is irreversible data destruction. In the context of a persistent state machine managing complex workflows, deletion of tasks represents loss of structured workflow state that cannot be restored.
From the tool's definition Tool name 'remove_tasks' and description states it will 'Remove multiple tasks from the active checklist' - this is irreversible deletion of data from the workflow state machine.
Attacks that exploit this kind of access
Remove multiple tasks from the active checklist. Safe for batch deletion, as remaining tasks are dynamically re-indexed only after all specified removals are processed. It is categorised as a Destructive tool in the Subconductor MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Subconductor MCP server in PolicyLayer and add a rule for remove_tasks: 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 Subconductor. Nothing to install.
remove_tasks 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 remove_tasks 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 remove_tasks. 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.
remove_tasks is provided by the Subconductor MCP server (paulbenchea/mcp-subconductor). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →