Permanently deletes a task file. For parent tasks, use cascade:true to delete the entire folder with subtasks. This operation cannot be undone.
AI agents call task_delete to permanently remove resources in Scopecraft Command — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes task files and optionally entire folder hierarchies without possibility of recovery. This is a classic destructive operation that cannot be reversed. While not financial in impact, the irreversible nature and potential to delete multiple related items (subtasks via cascade) makes it high severity.
From the tool's definition "Permanently deletes a task file" and "This operation cannot be undone" and "delete the entire folder with subtasks" indicate irreversible deletion of data.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access task_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Scopecraft Command, and nothing reaches the server without passing your rules. This is the rule we recommend for task_delete:
{
"version": "1",
"default": "deny",
"hide": [
"task_delete"
]
} task_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently deletes a task file. For parent tasks, use cascade:true to delete the entire folder with subtasks. This operation cannot be undone. It is categorised as a Destructive tool in the Scopecraft Command MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Scopecraft Command MCP server in PolicyLayer and add a rule for task_delete: 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 Scopecraft Command. Nothing to install.
task_delete 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_delete 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_delete. 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_delete is provided by the Scopecraft Command MCP server (scopecraft/command). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 Scopecraft Command tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
18 Scopecraft Command tools catalogued and risk-classified — across an index of 42,500+ MCP servers.