AI agents call deleteTask to permanently remove resources in Task API Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion operations are categorized as Destructive because they irreversibly remove data and cannot be undone. Even with an empty description, the name 'deleteTask' clearly indicates this tool deletes task records. In the context of a task management system alongside createTask, listTasks, and updateTask, deleteTask would remove task entries permanently.
From the tool's definition Tool name is 'deleteTask' which indicates deletion of task data. The description is empty, but the name unambiguously signals an irreversible operation that removes data.
Documented attack patterns abuse exactly the kind of access deleteTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task API Server, and nothing reaches the server without passing your rules. This is the rule we recommend for deleteTask:
{
"version": "1",
"default": "deny",
"hide": [
"deleteTask"
]
}deleteTask 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.
deleteTask. It is categorised as a Destructive tool in the Task API Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Task API Server 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 API Server. 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 API Server MCP server (milkosten/task-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Task API 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.
4 Task API Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.