AI agents call delete-topic to permanently remove resources in Kafka MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
delete-topic performs an irreversible action that cannot be undone—deleting a Kafka topic destroys the topic, its configuration, and potentially stored messages. This matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the description is empty, the tool name itself is unambiguous.
From the tool's definition Tool name is 'delete-topic'; sibling tools on the Kafka MCP server include topic management operations (create-topic, list-topics, topic-config). The name 'delete-topic' directly indicates irreversible deletion of Kafka topics and their associated data.
Documented attack patterns abuse exactly the kind of access delete-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 delete-topic:
{
"version": "1",
"default": "deny",
"hide": [
"delete-topic"
]
}delete-topic disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete-topic. It is categorised as a Destructive tool in the Kafka MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kafka MCP Server MCP server in PolicyLayer and add a rule for delete-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.
delete-topic is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-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 delete-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.
delete-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.