AI agents use update_dataset_topic_tags 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.
This tool modifies metadata (topic tags) in a Kafka cluster managed through Lenses. Metadata updates are reversible (tags can be changed or removed later), placing this in the Write category rather than Read (no retrieval-only) or Destructive (reversible).
From the tool's definition Tool name 'update_dataset_topic_tags' and description 'Update topic tags (in metadata)' indicate modification of metadata. The verb 'update' and action of changing tags represent reversible data modification rather than retrieval or deletion.
Documented attack patterns abuse exactly the kind of access update_dataset_topic_tags 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_dataset_topic_tags:
{
"version": "1",
"default": "deny",
"tools": {
"update_dataset_topic_tags": {
"limits": [
{
"counter": "update_dataset_topic_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_dataset_topic_tags 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 tags (in metadata). 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_dataset_topic_tags: 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_dataset_topic_tags 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_dataset_topic_tags 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_dataset_topic_tags. 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_dataset_topic_tags 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.