list_topics
AI agents call list_topics to retrieve information from Kafka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about Kafka topics without modifying, executing, or deleting anything. It is a read-only query operation. While confidence could be slightly higher with an explicit description, the name and sibling tool patterns (e.g., create_topic, delete_topic, list_consumer_groups) strongly indicate this is a simple list/retrieve operation with no blast radius if misused by an AI agent.
From the tool's definition Tool name 'list_topics' indicates a listing/querying operation with no side effects. The server description mentions 'manage topics, monitor consumer groups, and stream messages' and 'broker metadata inspection', and list_topics fits the metadata inspection…
Attacks that exploit this kind of access
list_topics. It is categorised as a Read tool in the Kafka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for list_topics: 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 Kafka MCP Server. Nothing to install.
list_topics 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 list_topics 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 list_topics. 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.
list_topics is provided by the Kafka MCP Server MCP server (jilanisayyad/kafka-mcp-server). 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 →