New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_kafka_topic

Delete a Kafka topic.

SERVERVultr MCP SOURCErsp2k/mcp-vultr
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about delete_kafka_topic

What does the delete_kafka_topic tool do? +

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.

How do I enforce a policy on delete_kafka_topic? +

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.

What risk level is delete_kafka_topic? +

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.

Can I rate-limit delete_kafka_topic? +

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.

How do I block delete_kafka_topic completely? +

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.

What MCP server provides delete_kafka_topic? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Vultr's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.