Critical Risk →

delete_user_policy

delete_user_policy

How to control delete_user_policy ↓

What delete_user_policy does on AWS

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

Critical Risk

Why delete_user_policy needs a policy

Deleting user policies irreversibly removes access controls and cannot be undone without re-attachment. This is a destructive operation with significant blast radius in an AWS IAM context—an agent misusing this could revoke critical access for users or services. High severity due to the potential for widespread privilege denial.

From the tool's definition Tool name 'delete_user_policy' explicitly indicates deletion of an IAM policy attachment, which is irreversible.

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

How to control delete_user_policy

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

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

delete_user_policy 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 AWS — 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.

Related tools and policies

Go deeper

Questions about delete_user_policy

What does the delete_user_policy tool do? +

delete_user_policy. 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_policy? +

Register the AWS MCP server in PolicyLayer and add a rule for delete_user_policy: 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_policy? +

delete_user_policy 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_policy? +

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

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

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

Enforce policy on every AWS tool call.

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

Free to start. No card required.

300 AWS tools catalogued and risk-classified — across an index of 43,000+ 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.