AI agents call delete_user to permanently remove resources in AWS S3 Tables MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'delete_user' explicitly signals deletion of a user, which is an irreversible destructive action. Although the description is empty, the tool name combined with the server's AWS context (particularly sibling IAM tools) provides high confidence this removes user accounts or identities, affecting access controls, authentication, and potentially data access.
From the tool's definition Tool name 'delete_user' combined with AWS IAM context (evidenced by sibling tools like 'add_inline_policy', 'add_user_to_group' which are identity management operations) indicates irreversible deletion of a user entity.
Documented attack patterns abuse exactly the kind of access delete_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS S3 Tables MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_user:
{
"version": "1",
"default": "deny",
"hide": [
"delete_user"
]
}delete_user 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. It is categorised as a Destructive tool in the AWS S3 Tables MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS S3 Tables MCP Server 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 S3 Tables MCP Server. Nothing to install.
delete_user 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 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. 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 is provided by the AWS S3 Tables MCP Server MCP server (awslabs.s3-tables-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS S3 Tables 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 S3 Tables MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.