AI agents use create_kafka_connector 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.
The tool name starts with 'create', indicating it creates a new Kafka connector. Based on naming conventions and sibling tools (create_environment, create_sql_processor, create_topic), this is a Write operation that provisions a new connector in the Kafka ecosystem. The description is empty, so confidence is reduced. Severity is high because misconfigured connectors can affect data pipelines across clusters.
From the tool's definition Tool name: create_kafka_connector — 'create' prefix suggests creating a new Kafka connector resource.
Documented attack patterns abuse exactly the kind of access create_kafka_connector 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 create_kafka_connector:
{
"version": "1",
"default": "deny",
"tools": {
"create_kafka_connector": {
"limits": [
{
"counter": "create_kafka_connector_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_kafka_connector 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.
create_kafka_connector. 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 create_kafka_connector: 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.
create_kafka_connector 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 create_kafka_connector 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 create_kafka_connector. 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.
create_kafka_connector 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.