This record as markdown: /tools/rsp2k-mcp-vultr/delete-kafka-topic.md
What delete_kafka_topic does on Vultr MCP
AI agents call delete_kafka_topic to permanently remove resources in Vultr MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_kafka_topic is rated Critical
Deleting a Kafka topic is a destructive action that cannot be undone—it permanently removes the topic and any messages within it. This has high blast radius in a production environment where an AI agent could inadvertently delete critical message streams. While not financial, it exceeds Execute severity because the action is irreversible.
From the tool's definition Tool name is 'delete_kafka_topic' and description states 'Delete a Kafka topic.' The verb 'delete' unambiguously indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_kafka_topic safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_kafka_topic, this is the rule to start with:
delete_kafka_topic is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every delete_kafka_topic call is checked against it from then on.
Questions about delete_kafka_topic
Delete a Kafka topic. It is categorised as a Destructive tool in the Vultr MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Vultr MCP server in PolicyLayer and add a rule for delete_kafka_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 Vultr MCP. Nothing to install.
delete_kafka_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_kafka_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_kafka_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_kafka_topic is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vultr, and thousands of servers like it.
Across the catalogue