Delete a task from a Microsoft Todo list. This will remove the task and all its checklist items (subtasks).
AI agents call delete-task to permanently remove resources in Microsoft Todo MCP Service — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data without possibility of recovery through the tool itself. While the blast radius is limited to a single task and its subtasks (not the entire list), the irreversible nature of deletion classifies it as Destructive rather than Write.
From the tool's definition Tool name 'delete-task' and description states 'Delete a task from a Microsoft Todo list. This will remove the task and all its checklist items (subtasks).' The use of 'Delete' and 'remove' indicates irreversible data destruction.
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 Microsoft Todo MCP Service, 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 from a Microsoft Todo list. This will remove the task and all its checklist items (subtasks). It is categorised as a Destructive tool in the Microsoft Todo MCP Service MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Microsoft Todo MCP Service 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 Microsoft Todo MCP Service. 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 Microsoft Todo MCP Service MCP server (jhirono/todomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Microsoft Todo MCP Service, 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.
13 Microsoft Todo MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.