Delete a task list and all its tasks
AI agents call delete_task_list to permanently remove resources in TasksMultiServer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes a task list and cascades deletion to all contained tasks. Deletion is permanent and cannot be undone. The blast radius is significant: an AI agent could accidentally or maliciously wipe entire task lists and their contents. This is the most severe category applicable (Destructive > Execute > Write > Read).
From the tool's definition Tool name is 'delete_task_list' and description states 'Delete a task list and all its tasks' — explicit deletion of data and all child entities with no recovery mechanism implied.
Attacks that exploit this kind of access
Delete a task list and all its tasks. It is categorised as a Destructive tool in the TasksMultiServer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TasksMultiServer 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 TasksMultiServer. 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 TasksMultiServer MCP server (keyurgolani/tasksmultiserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →