get_kafka_connector_target_definition
AI agents call get_kafka_connector_target_definition to retrieve information from Lenses MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' verb indicates a retrieval operation that queries existing connector configuration. Even though the description is empty, the tool name structure strongly suggests it fetches read-only metadata about a connector target definition, consistent with querying Kafka cluster state. No capability to modify, delete, or execute operations is implied. Confidence is slightly reduced due to the empty description.
From the tool's definition Tool name 'get_kafka_connector_target_definition' uses the 'get_' prefix, which conventionally indicates retrieval of data without modification.
Documented attack patterns abuse exactly the kind of access get_kafka_connector_target_definition 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 get_kafka_connector_target_definition:
{
"version": "1",
"default": "deny",
"tools": {
"get_kafka_connector_target_definition": {}
}
}get_kafka_connector_target_definition is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_kafka_connector_target_definition. It is categorised as a Read tool in the Lenses MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lenses MCP Server MCP server in PolicyLayer and add a rule for get_kafka_connector_target_definition: 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.
get_kafka_connector_target_definition is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_kafka_connector_target_definition 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 get_kafka_connector_target_definition. 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.
get_kafka_connector_target_definition 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.