Delete a development plan (moves to trash)
AI agents call delete_plan to permanently remove resources in Planning Game — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (a development plan) from active state, even though it may be recoverable from a trash bin. Destructive is the appropriate category as it matches the primary function of removing/deleting data. Severity is high because deletion of a plan could disrupt project workflows and team coordination, though the trash mechanism provides some recovery option.
From the tool's definition Tool name explicitly includes 'delete' and description states 'Delete a development plan (moves to trash)'. The action removes a plan from active use, and while recoverable from trash, represents irreversible removal from the working context.
Attacks that exploit this kind of access
Delete a development plan (moves to trash). It is categorised as a Destructive tool in the Planning Game MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Planning Game 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 Planning Game. 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 Planning Game MCP server (planning-game-mcp). 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 →