delete-instance-tag

THE RISK

Critical Risk

Why delete-instance-tag needs a policy

Deletion of instance tags is destructive because it permanently removes metadata that cannot be recovered without re-applying the tags. While less severe than deleting an instance itself, tag deletion removes operational metadata that may be critical for cost allocation, compliance tracking, automation rules, or resource identification.

From the tool's definition Tool name 'delete-instance-tag' contains 'delete', and description states 'Delete instance tag'. The action irreversibly removes metadata from an AWS EC2 instance.

Documented attack patterns abuse exactly the kind of access delete-instance-tag gives an agent:

POLICY

How to control delete-instance-tag

PolicyLayer is an MCP gateway — it sits between your AI agents and AWS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-instance-tag:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-instance-tag"
  ]
}

delete-instance-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 AWS 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 AWS MCP Server tools

Destructive delete-ami Delete an AMI Destructive delete-bucket Delete an S3 bucket in the given region Destructive delete-db-instance Delete a given RDS DB instance in the given region Destructive delete-internet-gateway Delete an internet gateway by ID in the given region Destructive delete-key-pair Delete a key pair in the given region Destructive delete-route-table Delete a route table in the given region Destructive delete-security-group Delete a security group in the given region Destructive delete-subnet Delete a subnet by subnet ID in the given region

All 54 AWS 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 AWS 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-instance-tag

What does the delete-instance-tag tool do? +

Delete instance tag. It is categorised as a Destructive tool in the AWS 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-instance-tag? +

Register the AWS MCP Server MCP server in PolicyLayer and add a rule for delete-instance-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 AWS MCP Server. Nothing to install.

What risk level is delete-instance-tag? +

delete-instance-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-instance-tag? +

Yes. Add a rate_limit block to the delete-instance-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-instance-tag completely? +

Set action: deny in the PolicyLayer policy for delete-instance-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-instance-tag? +

delete-instance-tag is provided by the AWS MCP Server MCP server (lokeswaran-aj/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AWS MCP Server tool call.

Start from AWS 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 →