Remove a todo item from the current plan
AI agents call remove_todo to permanently remove resources in Software Planning Tool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a todo item permanently deletes task information, which cannot be undone and represents an irreversible data loss operation. While the blast radius is limited to a single task within a development plan (not system-wide or financial), the destructive nature of permanent deletion elevates this beyond Write category. An AI agent could accidentally remove critical task items, disrupting project planning.
From the tool's definition Tool name 'remove_todo' and description 'Remove a todo item from the current plan' indicate irreversible deletion of task data from the planning system.
Documented attack patterns abuse exactly the kind of access remove_todo gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Software Planning Tool, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_todo:
{
"version": "1",
"default": "deny",
"hide": [
"remove_todo"
]
}remove_todo 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.
Remove a todo item from the current plan. It is categorised as a Destructive tool in the Software Planning Tool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Software Planning Tool MCP server in PolicyLayer and add a rule for remove_todo: 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 Software Planning Tool. Nothing to install.
remove_todo 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 remove_todo 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 remove_todo. 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.
remove_todo is provided by the Software Planning Tool MCP server (nighttrek/software-planning-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 Software Planning Tool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 Software Planning Tool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.