Critical Risk →

delete_tag

Delete a tag by project ID and tag ID

How to control delete_tag ↓

AI agents call delete_tag 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.

Critical Risk

The tool performs an irreversible deletion of a tag. While the blast radius is limited to tag metadata (not data loss at scale), deletion cannot be undone. This qualifies as Destructive rather than Write. Severity is medium because tag deletion is reversible at the application level (re-create the tag) but represents permanent removal of organizational metadata in the current state.

From the tool's definition Tool name contains 'delete' and description states 'Delete a tag by project ID and tag ID'. The action irreversibly removes a tag from the system.

Documented attack patterns abuse exactly the kind of access delete_tag 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_tag:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_tag"
  ]
}

delete_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Roadmap Skill — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_tag tool do? +

Delete a tag by project ID and tag 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.

How do I enforce a policy on delete_tag? +

Register the Roadmap Skill MCP server in PolicyLayer and add a rule for delete_tag: 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.

What risk level is delete_tag? +

delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_tag? +

Yes. Add a rate_limit block to the delete_tag 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.

How do I block delete_tag completely? +

Set action: deny in the PolicyLayer policy for delete_tag. 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.

What MCP server provides delete_tag? +

delete_tag 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.

Enforce policy on every Roadmap Skill tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.