AI agents call get_issue_frequency 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.
The naming pattern and server context (monitoring, health analysis) indicate this retrieves metrics or statistics about issue frequencies rather than modifying state. No evidence suggests creation, deletion, execution, or financial impact. The low confidence reflects the uninformative empty description, but the pattern is consistent with read-only monitoring tools.
From the tool's definition Tool name 'get_issue_frequency' suggests querying frequency metrics; empty description limits certainty. Sibling tools like 'get_broker_resources', 'get_cluster_details', and 'describe_kafka_topic' are all Read operations on Kafka clusters.
Attacks that exploit this kind of access
get_issue_frequency. 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_issue_frequency: 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_issue_frequency 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_issue_frequency 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_issue_frequency. 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_issue_frequency 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 →