Delete a local roadmap and its milestone/release config.
AI agents call delete_roadmap to permanently remove resources in Todos — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a roadmap and associated configuration without possibility of recovery or undo. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone (delete, drop, purge, force-push).' The high severity reflects that losing a roadmap and its release configuration could disrupt project planning and deployment pipelines.
From the tool's definition Tool name is 'delete_roadmap' and description states 'Delete a local roadmap and its milestone/release config' — the word 'Delete' combined with the irreversible nature of removing configuration data.
Attacks that exploit this kind of access
Delete a local roadmap and its milestone/release config. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for delete_roadmap: 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 Todos. Nothing to install.
delete_roadmap 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_roadmap 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_roadmap. 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_roadmap is provided by the Todos MCP server (@hasna/todos). 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 →