AI agents call get_lag_trend_analysis 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 appears to retrieve and analyze consumer lag trends over time without modifying any Kafka cluster state or data. It falls under the 'Read' category as a query/analysis operation. Confidence is lowered slightly (not 0.95+) because the description is empty, requiring inference from the name and server context. Severity is low because reading trend data poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_lag_trend_analysis' and sibling tools 'detect_transient_vs_persistent', 'describe_kafka_topic', and 'get_consumer_lag' indicate read-only analytical operations.
Attacks that exploit this kind of access
get_lag_trend_analysis. 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_lag_trend_analysis: 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_lag_trend_analysis 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_lag_trend_analysis 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_lag_trend_analysis. 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_lag_trend_analysis 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 →