AI agents call kafka_health_check 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 health status information about a Kafka connection without modifying data, executing code, or triggering external operations. It is a passive diagnostic query analogous to a GET request, falling squarely into the Read category. The low severity reflects minimal blast radius—a malicious agent could only gain visibility into cluster health, not affect operations or data.
From the tool's definition Tool name 'kafka_health_check' and description 'Check the health status of the Kafka connection' indicate a monitoring/status query operation with no modification or execution of external commands.
Attacks that exploit this kind of access
Check the health status of the Kafka connection. 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 kafka_health_check: 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.
kafka_health_check 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 kafka_health_check 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 kafka_health_check. 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.
kafka_health_check 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 →