AI agents call delete_plan to permanently remove resources in Valkey MCP Task Management Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a plan and potentially all associated tasks and notes from the Valkey persistence layer. This operation cannot be undone and represents a complete loss of data for that plan. Deletion is categorically destructive. While the blast radius is somewhat limited to a single plan, the irreversible nature and potential loss of multiple related entities (tasks, notes) justifies 'high' severity.
From the tool's definition Tool name is 'delete_plan' with description 'Delete a plan by ID'. The verb 'delete' combined with operating on a plan entity (which likely contains tasks, notes, and other associated data based on the sibling tools and server description) indicates…
Documented attack patterns abuse exactly the kind of access delete_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Valkey MCP Task Management Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_plan:
{
"version": "1",
"default": "deny",
"hide": [
"delete_plan"
]
}delete_plan 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 plan by ID. It is categorised as a Destructive tool in the Valkey MCP Task Management Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Valkey MCP Task Management Server MCP server in PolicyLayer and add a rule for delete_plan: 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 Valkey MCP Task Management Server. Nothing to install.
delete_plan 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_plan 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_plan. 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_plan is provided by the Valkey MCP Task Management Server MCP server (jbrinkman/valkey-ai-tasks). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Valkey MCP Task Management Server, 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.
17 Valkey MCP Task Management Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.