AI agents use create-topic to create or update resources in Kafka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kafka MCP Server environment.
create-topic creates a new Kafka topic, which is a reversible write operation (topics can be deleted via the sibling delete-topic tool). It modifies cluster state by adding a new message queue but does not irreversibly destroy data or execute arbitrary code. The empty description reduces confidence slightly, but the tool name and server context are sufficiently clear.
From the tool's definition Tool name 'create-topic' indicates data structure creation. Server context shows this is a Kafka MCP server for publishing/consuming messages. Creating a topic is a write operation that adds a new message queue to the Kafka cluster.
Documented attack patterns abuse exactly the kind of access create-topic gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kafka MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create-topic:
{
"version": "1",
"default": "deny",
"tools": {
"create-topic": {
"limits": [
{
"counter": "create-topic_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-topic stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
create-topic. It is categorised as a Write tool in the Kafka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for create-topic: 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.
create-topic is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create-topic 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 create-topic. 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.
create-topic is provided by the Kafka MCP Server MCP server (pavanjava/kafka_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kafka MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Kafka MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.