This record as markdown: /tools/108yen-task-orchestrator-mcp/deletetask.md
What deleteTask does on Task Orchestrator
AI agents call deleteTask to permanently remove resources in Task Orchestrator, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteTask is rated Critical
This tool permanently removes task data with no apparent undo mechanism. Deletion is irreversible and falls under the Destructive category, which is more severe than Write (which covers reversible modifications). The high severity reflects that an AI agent could inadvertently destroy important task records, affecting workflow orchestration and data integrity. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name is 'deleteTask' and description states 'Delete a task by its ID'. The verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs deleteTask safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Task Orchestrator, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For deleteTask, this is the rule to start with:
deleteTask 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 Task Orchestrator, apply this rule, and every deleteTask call is checked against it from then on.
Questions about deleteTask
Delete a task by its ID. It is categorised as a Destructive tool in the Task Orchestrator MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Task Orchestrator MCP server in PolicyLayer and add a rule for deleteTask: 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 Task Orchestrator. Nothing to install.
deleteTask 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 deleteTask 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 deleteTask. 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.
deleteTask is provided by the Task Orchestrator MCP server (108yen/task-orchestrator-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Task Orchestrator, and thousands of servers like it.
Across the catalogue