delete_consumer_group_offsets

THE RISK

Critical Risk

Why delete_consumer_group_offsets needs a policy

Deleting consumer group offsets is a destructive action that cannot be undone—it permanently removes tracking state for message consumption in Kafka topics. This affects the ability to resume from saved positions and can cause message reprocessing or data loss in downstream applications. The tool belongs in the Destructive category as it irreversibly modifies critical Kafka metadata.

From the tool's definition Tool name contains 'delete_consumer_group_offsets', which explicitly indicates irreversible deletion of consumer group offset metadata in Kafka.

Documented attack patterns abuse exactly the kind of access delete_consumer_group_offsets gives an agent:

POLICY

How to control delete_consumer_group_offsets

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_offsets:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_consumer_group_offsets"
  ]
}

delete_consumer_group_offsets disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Lenses MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Lenses MCP Server tools

Destructive delete_consumer_group Delete a consumer group. Destructive delete_consumer_partition_offset delete_consumer_partition_offset Destructive delete_kafka_connector Deletes a Kafka connector. Destructive delete_sql_processor Removes an existing SQL processor. Execute execute_sql Executes SQL statements/queries using Lenses WebSocket API. Execute restart_kafka_connector_task restart_kafka_connector_task Execute resend_message resend_message Execute create_sql_processor create_sql_processor

All 42 Lenses MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Lenses MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_consumer_group_offsets

What does the delete_consumer_group_offsets tool do? +

delete_consumer_group_offsets. 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.

How do I enforce a policy on delete_consumer_group_offsets? +

Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for delete_consumer_group_offsets: 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.

What risk level is delete_consumer_group_offsets? +

delete_consumer_group_offsets is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_consumer_group_offsets? +

Yes. Add a rate_limit block to the delete_consumer_group_offsets 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.

How do I block delete_consumer_group_offsets completely? +

Set action: deny in the PolicyLayer policy for delete_consumer_group_offsets. 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.

What MCP server provides delete_consumer_group_offsets? +

delete_consumer_group_offsets 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.

Enforce policy on every Lenses MCP Server tool call.

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.

CHECK YOUR STACK →