AI agents use update_topic_config 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.
Updating topic configuration in Kafka affects message retention, replication, compression, and other critical parameters. While reversible, misconfiguration could impact data availability, throughput, or compliance. This is a Write operation (modify existing settings) rather than Execute (which would apply arbitrary logic) or Destructive (configuration changes are not irreversible).
From the tool's definition Tool name 'update_topic_config' and description 'Update topic configuration' indicate modification of existing Kafka topic settings. This is a reversible change operation (configuration can be modified again), not a deletion.
Documented attack patterns abuse exactly the kind of access update_topic_config 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 update_topic_config:
{
"version": "1",
"default": "deny",
"tools": {
"update_topic_config": {
"limits": [
{
"counter": "update_topic_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_topic_config 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.
Free to start. No card required.
Update topic configuration. 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.
Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for update_topic_config: 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.
update_topic_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_topic_config 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 update_topic_config. 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.
update_topic_config 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.