Delete a checklist item (subtask) from a task. This removes just the specific subtask, not the parent task.
AI agents call delete-checklist-item 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 deletes data (a checklist item/subtask) that cannot be undone. While the blast radius is somewhat contained to a single subtask rather than an entire task, deletion is inherently destructive and irreversible. Destructive is the appropriate category, and 'high' severity reflects that misuse would result in permanent data loss, though the scope is limited to one subtask at a time.
From the tool's definition Tool name is 'delete-checklist-item' and description states 'Delete a checklist item (subtask) from a task. This removes just the specific subtask, not the parent task.' The verb 'Delete' and phrase 'removes' indicate irreversible data deletion.
Documented attack patterns abuse exactly the kind of access delete-checklist-item 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-checklist-item:
{
"version": "1",
"default": "deny",
"hide": [
"delete-checklist-item"
]
} delete-checklist-item 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 checklist item (subtask) from a task. This removes just the specific subtask, not the parent task. 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-checklist-item: 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-checklist-item 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-checklist-item 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-checklist-item. 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-checklist-item 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.