AI agents call get_recurring_issues 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 tool appears designed to retrieve and analyze historical issue patterns from the Kafka cluster for monitoring and reporting purposes. The verb 'get' and context of KafkaIQ's stated capability for 'health monitoring' and 'temporal trend detection' indicate this is a non-destructive read operation that queries existing data.
From the tool's definition Tool name 'get_recurring_issues' implies retrieval/query of historical data about Kafka cluster issues. No description provided, but naming pattern and sibling tools (describe_kafka_topic, get_broker_resources, get_cluster_details, get_consumer_lag) all…
Attacks that exploit this kind of access
get_recurring_issues. 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_recurring_issues: 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_recurring_issues 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_recurring_issues 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_recurring_issues. 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_recurring_issues 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 →