delete_user

A destructive tool on the AWS MCP server.

SERVERAWS SOURCE@awslabs/mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/aws/delete-user.md

WHAT IT DOES

What delete_user does on AWS

AI agents call delete_user to permanently remove resources in AWS, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_user is rated Critical

User deletion is a destructive operation—it removes authentication credentials, access policies, and typically cannot be reversed without recreation. This is more severe than Write (which is reversible) and exceeds Execute (which has variable effects).

From the tool's definition Tool name 'delete_user' indicates irreversible removal of a user identity/account. The empty description prevents confirmation of scope (single user vs. batch, partial vs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_user safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AWS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_user, this is the rule to start with:

delete_user Hidden

delete_user is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_user"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every delete_user call is checked against it from then on.

FAQ

Questions about delete_user

What does the delete_user tool do? +

delete_user is a destructive tool on the AWS MCP server. It is categorised as a Destructive tool in the AWS 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_user? +

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

What risk level is delete_user? +

delete_user 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_user? +

Yes. Add a rate_limit block to the delete_user 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_user completely? +

Set action: deny in the PolicyLayer policy for delete_user. 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_user? +

delete_user is provided by the AWS MCP server (@awslabs/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AWS, and thousands of servers like it.

This server

All 300 AWS tools → Critical-risk tools on this server →

Across the catalogue

delete_mysql_user on cPanel MCP Server →sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern infrastructure agents →Blast radius →Tool call approval →