AI agents call delete_task to permanently remove resources in MCP Orchestrator Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes task records from the orchestration system. Although it includes a guard condition ('if it has no dependents'), the core action is irreversible deletion of data. Once a task is deleted, its history and associated metadata are lost. This cannot be undone through normal means and represents a destructive operation.
From the tool's definition Tool name is 'delete_task' and description states it 'Delete a task' — uses the keyword 'Delete' which indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Orchestrator Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_task:
{
"version": "1",
"default": "deny",
"hide": [
"delete_task"
]
}delete_task 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.
Delete a task if it has no dependents. It is categorised as a Destructive tool in the MCP Orchestrator Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Orchestrator Server MCP server in PolicyLayer and add a rule for delete_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 MCP Orchestrator Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_task is provided by the MCP Orchestrator Server MCP server (mokafari/orchestrator-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Orchestrator Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 MCP Orchestrator Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.