Delete consumer from group.
AI agents call stream_group_delete_consumer to permanently remove resources in AWS Labs MySQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a consumer from a stream group. Deletion is an irreversible operation that cannot be undone without restoring from backups or manual intervention. While the blast radius is limited to consumer group membership (not system-wide), the destructive nature of the action and its permanence warrant the Destructive category with high severity.
From the tool's definition Tool name is 'stream_group_delete_consumer' with description 'Delete consumer from group.' The verb 'delete' indicates an irreversible removal operation.
Documented attack patterns abuse exactly the kind of access stream_group_delete_consumer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AWS Labs MySQL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for stream_group_delete_consumer:
{
"version": "1",
"default": "deny",
"hide": [
"stream_group_delete_consumer"
]
} stream_group_delete_consumer 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 consumer from group. It is categorised as a Destructive tool in the AWS Labs MySQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the AWS Labs MySQL MCP Server MCP server in PolicyLayer and add a rule for stream_group_delete_consumer: 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 Labs MySQL MCP Server. Nothing to install.
stream_group_delete_consumer 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_delete_consumer 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_delete_consumer. 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_delete_consumer is provided by the AWS Labs MySQL MCP Server MCP server (awslabs.mysql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AWS Labs MySQL 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 Labs MySQL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.