This record as markdown: /tools/aws/stream-group-destroy.md
What stream_group_destroy does on AWS
AI agents call stream_group_destroy 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 stream_group_destroy is rated Critical
The tool performs an irreversible deletion operation on a consumer group. Destruction of infrastructure resources cannot be undone and will disrupt any applications or workflows dependent on that consumer group.
From the tool's definition Tool name contains 'destroy' and description states 'Destroy consumer group' — this irreversibly deletes a consumer group resource.
Attacks that exploit this kind of access
The rule that runs stream_group_destroy 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 stream_group_destroy, this is the rule to start with:
stream_group_destroy 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 stream_group_destroy call is checked against it from then on.
Questions about stream_group_destroy
Destroy consumer group. Args: key: The name of the key group_name: Name of consumer group Returns: Success message or error message. 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 stream_group_destroy: 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.
stream_group_destroy 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 stream_group_destroy 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 stream_group_destroy. 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.
stream_group_destroy 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