Medium Risk

update_consumer_group_offsets

update_consumer_group_offsets

How to control update_consumer_group_offsets ↓

What update_consumer_group_offsets does on Lenses MCP Server

AI agents use update_consumer_group_offsets to create or update resources in Lenses MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lenses MCP Server environment.

Medium Risk

Why update_consumer_group_offsets needs a policy

Updating consumer group offsets modifies Kafka consumer state, which affects message replay and processing order for consumers. This is reversible (offsets can be reset again) and doesn't destroy data, so it qualifies as Write rather than Destructive. However, severity is high because incorrect offset modifications could cause message loss, reprocessing, or denial of service to dependent applications.

From the tool's definition Tool name is 'update_consumer_group_offsets' which modifies consumer group offset state in Kafka. Related destructive tools on the server include 'delete_consumer_group_offsets' and 'delete_consumer_partition_offset', suggesting this tool performs state…

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

How to control update_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 update_consumer_group_offsets:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_consumer_group_offsets": {
      "limits": [
        {
          "counter": "update_consumer_group_offsets_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_consumer_group_offsets stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

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

Free to start. No card required.

Related tools and policies

Go deeper

Questions about update_consumer_group_offsets

What does the update_consumer_group_offsets tool do? +

update_consumer_group_offsets. It is categorised as a Write tool in the Lenses MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_consumer_group_offsets? +

Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for update_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 update_consumer_group_offsets? +

update_consumer_group_offsets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_consumer_group_offsets? +

Yes. Add a rate_limit block to the update_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 update_consumer_group_offsets completely? +

Set action: deny in the PolicyLayer policy for update_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 update_consumer_group_offsets? +

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

Free to start. No card required.

42 Lenses MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.