AI agents call get_broker_resources 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 broker resource information (CPU, memory, disk, etc.) from a Kafka cluster for monitoring purposes. It has no side effects, does not execute commands, does not modify data, and does not trigger operational changes. It is a straightforward Read operation with minimal security risk, appropriate for health monitoring and observability use cases.
From the tool's definition Tool name 'get_broker_resources' and description 'Get resource information for a specific Kafka broker' indicate a query/retrieval operation that retrieves resource metrics and status data without modifying or executing operations.
Attacks that exploit this kind of access
Get resource information for a specific Kafka broker. 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 get_broker_resources: 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.
get_broker_resources 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_broker_resources 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_broker_resources. 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_broker_resources 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 →