Delete a task list (top-level container) from Microsoft Todo. This will remove the list and all tasks within it.
AI agents call delete-task-list to permanently remove resources in My MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data that cannot be recovered—an entire task list and all its contents. This is a classic destructive operation with no undo capability. Severity is high because an AI agent could accidentally delete all tasks in a list, causing loss of important work items and data.
From the tool's definition Tool name 'delete-task-list' and description explicitly states 'Delete a task list (top-level container) from Microsoft Todo.
Documented attack patterns abuse exactly the kind of access delete-task-list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and My MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-task-list:
{
"version": "1",
"default": "deny",
"hide": [
"delete-task-list"
]
} delete-task-list 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 list (top-level container) from Microsoft Todo. This will remove the list and all tasks within it. It is categorised as a Destructive tool in the My MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the My MCP server in PolicyLayer and add a rule for delete-task-list: 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 My MCP. Nothing to install.
delete-task-list 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-list 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-list. 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-list is provided by the My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My MCP, 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.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.