AI agents call delete_group to permanently remove resources in AWS Infrastructure as Code MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The name 'delete_group' follows the pattern of destructive operations that remove a resource permanently. In an AWS IAM context, deleting a group removes all group memberships and associated policies, which is irreversible. Given sibling tools like 'add_user_to_group' and 'add_inline_policy', this server manages IAM resources, making 'delete_group' highly likely to be a destructive IAM group deletion.
From the tool's definition Tool name 'delete_group' strongly implies irreversible deletion of a group resource (e.g., IAM group or similar AWS group entity). The description is empty and provides no additional context.
Documented attack patterns abuse exactly the kind of access delete_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Infrastructure as Code MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_group:
{
"version": "1",
"default": "deny",
"hide": [
"delete_group"
]
}delete_group 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_group. It is categorised as a Destructive tool in the AWS Infrastructure as Code MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Infrastructure as Code MCP Server MCP server in PolicyLayer and add a rule for delete_group: 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 Infrastructure as Code MCP Server. Nothing to install.
delete_group 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_group 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_group. 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_group is provided by the AWS Infrastructure as Code MCP Server MCP server (awslabs.aws-iac-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Infrastructure as Code 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 Infrastructure as Code MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.