Remove a task from the active checklist. Warning: Removing a task will automatically re-index the IDs of all subsequent tasks in the checklist.
AI agents call remove_task 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 destroys data (removes a task) irreversibly. While task removal might seem reversible through re-addition, the automatic re-indexing of subsequent task IDs means that the original task sequence and any references to those IDs are permanently altered. This is characteristic of Destructive category.
From the tool's definition Tool 'remove_task' performs an irreversible deletion action: 'Remove a task from the active checklist.' The description explicitly warns that this action has cascading side effects ('automatically re-index the IDs of all subsequent tasks'), indicating data…
Attacks that exploit this kind of access
Remove a task from the active checklist. Warning: Removing a task will automatically re-index the IDs of all subsequent tasks in the checklist. 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_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 Subconductor. Nothing to install.
remove_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 remove_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 remove_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.
remove_task 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 →