delete_tag

THE RISK

Critical Risk

Why delete_tag needs a policy

Deleting a tag is an irreversible destructive operation that permanently removes metadata. While the blast radius is moderate (tags are organizational metadata, not the resources themselves), the operation cannot be undone and fits the Destructive category.

From the tool's definition Tool name is 'delete_tag' with description 'Delete a Tag'. The verb 'Delete' explicitly indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete_tag gives an agent:

POLICY

How to control delete_tag

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, 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.

Create a free account and register Linode MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Linode MCP Server tools

Destructive cancel_account Cancel your account Destructive cancel_backups Cancel backups for a Linode instance Destructive cancel_object_storage Cancel Object Storage service Destructive delete_alert_definition Delete an alert definition Destructive delete_api_token Delete an API token Destructive delete_config_interface Delete an interface from a configuration profile Destructive delete_domain Delete a domain Destructive delete_domain_record Delete a domain record

All 416 Linode MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Linode MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_tag

What does the delete_tag tool do? +

Delete a Tag. It is categorised as a Destructive tool in the Linode MCP Server 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 Linode MCP Server 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 Linode MCP Server. 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 Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →