AI agents call cluster-health to retrieve information from Kafka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
'cluster-health' strongly implies a read/query operation that checks and returns the health status of the Kafka cluster. No description is provided, but in the context of sibling tools (list-topics, cluster-metadata, topic-config) which are all read operations, this tool fits the Read category. No side effects are expected from a health check. Confidence is moderate due to the empty description.
From the tool's definition Tool name is 'cluster-health'; description is empty. Based on the name and context of a Kafka MCP server, this tool likely retrieves health/status information about the Kafka cluster.
Documented attack patterns abuse exactly the kind of access cluster-health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kafka MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cluster-health:
{
"version": "1",
"default": "deny",
"tools": {
"cluster-health": {}
}
}cluster-health 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.
cluster-health. It is categorised as a Read tool in the Kafka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for cluster-health: 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 Kafka MCP Server. Nothing to install.
cluster-health 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 cluster-health 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 cluster-health. 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.
cluster-health is provided by the Kafka MCP Server MCP server (pavanjava/kafka_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kafka 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.
8 Kafka MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.