Delete a task list. Note: This will also delete all tasks in the list
AI agents call delete_task_list to permanently remove resources in VaultAssist — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a task list and cascades deletion to all contained tasks. The operation is irreversible and represents data loss. Although scoped to a single user's task list (multi-user isolation mitigates blast radius), the destructive nature and inability to undo the action place it in the Destructive category rather than Write.
From the tool's definition 'Delete a task list' with explicit note 'This will also delete all tasks in the list' — irreversibly removes data and all associated child records without recovery option.
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 VaultAssist, 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. Note: This will also delete all tasks in the list. It is categorised as a Destructive tool in the VaultAssist MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the VaultAssist 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 VaultAssist. 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 VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.