AI agents call broker_leadership_distribution to retrieve information from KafkaIQ without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports broker leadership metadata from a Kafka cluster without modifying, deleting, or executing any operations. It falls squarely into the Read category—a straightforward data retrieval tool used for monitoring and observability. The blast radius of misuse is minimal since it only provides cluster state information.
From the tool's definition Tool name 'broker_leadership_distribution' and description 'Return how many partitions each broker is the leader for' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Return how many partitions each broker is the leader for. It is categorised as a Read tool in the KafkaIQ MCP Server, which means it retrieves data without modifying state.
Register the KafkaIQ MCP server in PolicyLayer and add a rule for broker_leadership_distribution: 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 KafkaIQ. Nothing to install.
broker_leadership_distribution 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 broker_leadership_distribution 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 broker_leadership_distribution. 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.
broker_leadership_distribution is provided by the KafkaIQ MCP server (ojhaayush03/kafka_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →