AI agents call delete_consumer_group to permanently remove resources in Lenses MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a consumer group removes tracking state for message consumption in Kafka, and this action cannot be trivially undone. An AI agent misusing this tool could disrupt data pipeline monitoring, cause loss of offset history, and break consumer applications relying on that group. The high severity reflects the operational impact of losing consumer group metadata in a production Kafka environment.
From the tool's definition Tool name 'delete_consumer_group' explicitly deletes a consumer group, which is an irreversible operation.
Documented attack patterns abuse exactly the kind of access delete_consumer_group gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Lenses MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_consumer_group:
{
"version": "1",
"default": "deny",
"hide": [
"delete_consumer_group"
]
}delete_consumer_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 a consumer group. It is categorised as a Destructive tool in the Lenses MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for delete_consumer_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 Lenses MCP Server. Nothing to install.
delete_consumer_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_consumer_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_consumer_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_consumer_group is provided by the Lenses MCP Server MCP server (lensesio/lenses-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Lenses 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.
42 Lenses MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.