Delete a dependency planning view by project ID and view ID
AI agents call delete_dependency_view to permanently remove resources in Roadmap Skill — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on a dependency planning view. Once deleted, the view and its associated planning data cannot be recovered without external backups. This is a classic destructive action that removes data without the ability to undo it, making it more severe than Write (which is reversible) or Execute (which may have variable effects).
From the tool's definition Tool name is 'delete_dependency_view' and description states 'Delete a dependency planning view by project ID and view ID'. The verb 'Delete' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access delete_dependency_view gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Roadmap Skill, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_dependency_view:
{
"version": "1",
"default": "deny",
"hide": [
"delete_dependency_view"
]
} delete_dependency_view 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 dependency planning view by project ID and view ID. It is categorised as a Destructive tool in the Roadmap Skill MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Roadmap Skill MCP server in PolicyLayer and add a rule for delete_dependency_view: 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 Roadmap Skill. Nothing to install.
delete_dependency_view 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_dependency_view 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_dependency_view. 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_dependency_view is provided by the Roadmap Skill MCP server (shiquda/roadmap-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 Roadmap Skill tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 Roadmap Skill tools catalogued and risk-classified — across an index of 42,500+ MCP servers.