Critical Risk →

delete_bare_metal_server

Delete a bare metal server.

How to control delete_bare_metal_server ↓

What delete_bare_metal_server does on Vultr MCP

AI agents call delete_bare_metal_server 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.

Critical Risk

Why delete_bare_metal_server needs a policy

Deleting a bare metal server is a destructive action that cannot be undone and results in loss of the server instance and associated resources. This represents maximum severity due to the blast radius: loss of compute infrastructure, potential downtime, data loss if not backed up separately, and financial impact from service interruption. An AI agent misusing this tool could eliminate production infrastructure.

From the tool's definition Tool name explicitly contains 'delete' and description states 'Delete a bare metal server' — this irreversibly removes cloud infrastructure.

Documented attack patterns abuse exactly the kind of access delete_bare_metal_server gives an agent:

How to control delete_bare_metal_server

PolicyLayer is an MCP gateway — it sits between your AI agents and Vultr MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_bare_metal_server:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_bare_metal_server"
  ]
}

delete_bare_metal_server disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Vultr MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about delete_bare_metal_server

What does the delete_bare_metal_server tool do? +

Delete a bare metal server. 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_bare_metal_server? +

Register the Vultr MCP server in PolicyLayer and add a rule for delete_bare_metal_server: 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_bare_metal_server? +

delete_bare_metal_server 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_bare_metal_server? +

Yes. Add a rate_limit block to the delete_bare_metal_server 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_bare_metal_server completely? +

Set action: deny in the PolicyLayer policy for delete_bare_metal_server. 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_bare_metal_server? +

delete_bare_metal_server 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.

Enforce policy on every Vultr MCP tool call.

Start from Vultr MCP, 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.

284 Vultr MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.