This record as markdown: /tools/todos/delete-task-list.md
What delete_task_list does on Todos
AI agents call delete_task_list to permanently remove resources in Todos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_task_list is rated Critical
This tool performs permanent deletion of data structures (task lists) and their contents, which cannot be undone. This fits the Destructive category as defined—actions that irreversibly delete or overwrite data. The scope includes both the list and all associated tasks, amplifying the impact.
From the tool's definition Tool name 'delete_task_list' combined with description 'Permanently delete a task list and all its tasks.' indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_task_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_task_list, this is the rule to start with:
delete_task_list 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 Todos, apply this rule, and every delete_task_list call is checked against it from then on.
Questions about delete_task_list
Permanently delete a task list and all its tasks. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos 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 Todos. 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 Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
Across the catalogue