This record as markdown: /tools/aws/delete-resource.md
What delete_resource does on AWS
AI agents call delete_resource 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.
Why delete_resource is rated Critical
The tool name 'delete_resource' directly implies the ability to irreversibly remove or destroy resources. Given the AWS context and sibling tools (attach_user_policy, attach_group_policy, audit operations), this tool likely manages infrastructure or configuration resources. Deletion of AWS resources cannot be undone without restoration from backups.
From the tool's definition Tool name is 'delete_resource' which explicitly indicates irreversible deletion of data or resources. No description provided, but the name unambiguously suggests a destructive operation.
Attacks that exploit this kind of access
The rule that runs delete_resource 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_resource, this is the rule to start with:
delete_resource is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AWS, apply this rule, and every delete_resource call is checked against it from then on.
Questions about delete_resource
delete_resource 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.
Register the AWS MCP server in PolicyLayer and add a rule for delete_resource: 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.
delete_resource 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_resource 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_resource. 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_resource 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.
More on AWS, and thousands of servers like it.
Across the catalogue