Delete an S3 bucket
AI agents call s3_bucket_delete to permanently remove resources in AWS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
S3 bucket deletion is an irreversible destructive operation that permanently removes cloud infrastructure and all associated data. This is the most severe category. An AI agent misusing this tool could cause catastrophic data loss across an entire bucket and its contents. Critical severity is warranted because the blast radius is organizational-level infrastructure damage.
From the tool's definition Tool name is 's3_bucket_delete' and description states 'Delete an S3 bucket'. Deletion of cloud storage buckets is irreversible and cannot be undone. This action destroys data at scale with no recovery path.
Attacks that exploit this kind of access
Delete an S3 bucket. 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.
Register the AWS MCP Server MCP server in PolicyLayer and add a rule for s3_bucket_delete: 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.
s3_bucket_delete 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 s3_bucket_delete 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 s3_bucket_delete. 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.
s3_bucket_delete is provided by the AWS MCP Server MCP server (rishikavikondala/mcp-server-aws). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →