AI agents call delete_user_policy to permanently remove resources in AWS DynamoDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes IAM policy attachments or inline policies from an AWS user account. Such deletions cannot be undone without reapplying the policy, and improper deletion can lock out users, break application access, or alter security postures irreversibly. Despite the empty description, the name and AWS context provide high confidence that this is a destructive operation with significant blast radius.
From the tool's definition Tool name 'delete_user_policy' combined with AWS IAM context (inferred from sibling tools like 'add_inline_policy' and 'add_user_to_group') indicates irreversible deletion of an IAM policy. The word 'delete' is explicitly destructive.
Documented attack patterns abuse exactly the kind of access delete_user_policy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS DynamoDB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_user_policy:
{
"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.
Free to start. No card required.
delete_user_policy. It is categorised as a Destructive tool in the AWS DynamoDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS DynamoDB MCP Server 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 DynamoDB MCP Server. Nothing to install.
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.
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.
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.
delete_user_policy is provided by the AWS DynamoDB MCP Server MCP server (awslabs.dynamodb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS DynamoDB MCP Server, 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.
805 AWS DynamoDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.