Clear all completed tasks from a task list. The tasks will be marked as hidden
AI agents call clear_completed_tasks 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.
While the description says tasks are 'marked as hidden' rather than permanently deleted, 'clearing' completed tasks is a bulk irreversible operation that removes visibility of all completed tasks at once. The word 'clear' combined with bulk scope (all completed tasks) and lack of any undo mechanism described makes this effectively destructive.
From the tool's definition Clear all completed tasks from a task list. The tasks will be marked as hidden
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access clear_completed_tasks 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 clear_completed_tasks:
{
"version": "1",
"default": "deny",
"hide": [
"clear_completed_tasks"
]
} clear_completed_tasks 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.
Clear all completed tasks from a task list. The tasks will be marked as hidden. 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 clear_completed_tasks: 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.
clear_completed_tasks 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 clear_completed_tasks 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 clear_completed_tasks. 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.
clear_completed_tasks 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.