Get detailed topic info: partitions, leaders, replicas, ISR, configs.
AI agents call kafka_topic_info to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries Kafka topic metadata and configuration without any side effects or capability to alter state. It is purely informational, fitting the Read category definition of retrieving or querying data. The low severity reflects that information disclosure about topic structure poses minimal immediate risk to system operations.
From the tool's definition Tool description explicitly states 'Get detailed topic info' with read-only operations: 'partitions, leaders, replicas, ISR, configs.' No verbs indicating modification, deletion, or execution.
Attacks that exploit this kind of access
Get detailed topic info: partitions, leaders, replicas, ISR, configs. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for kafka_topic_info: 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 RedisNexus. Nothing to install.
kafka_topic_info 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 kafka_topic_info 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 kafka_topic_info. 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.
kafka_topic_info is provided by the RedisNexus MCP server (rajkumar-madhu/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 →