reboot_bare_metal_server

THE RISK

High Risk

Why reboot_bare_metal_server needs a policy

Rebooting a bare metal server triggers an external operation on physical infrastructure that causes service interruption. It is not destructive (no data loss) but it executes a real-world action with significant blast radius — any workloads running on that server will be disrupted. This falls squarely in Execute, and the high severity reflects the potential for downtime across all services hosted on that server.

From the tool's definition Reboot a bare metal server

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

POLICY

How to control reboot_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 reboot_bare_metal_server:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reboot_bare_metal_server": {
      "limits": [
        {
          "counter": "reboot_bare_metal_server_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

reboot_bare_metal_server stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

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

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Vultr MCP tools

Destructive delete Delete a block storage volume. Destructive delete_bare_metal_server Delete a bare metal server. Destructive delete_cdn_ssl_certificate Remove SSL certificate from a CDN zone. Destructive delete_cdn_zone Delete a CDN zone. Destructive delete_collection delete_collection Destructive delete_connection_pool Delete a connection pool. Destructive delete_dns_domain Delete a DNS domain and ALL its associated records Destructive delete_dns_record Delete a specific DNS record

All 284 Vultr MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Vultr MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about reboot_bare_metal_server

What does the reboot_bare_metal_server tool do? +

Reboot a bare metal server. It is categorised as a Execute tool in the Vultr MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reboot_bare_metal_server? +

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

reboot_bare_metal_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reboot_bare_metal_server? +

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

Set action: deny in the PolicyLayer policy for reboot_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 reboot_bare_metal_server? +

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

CHECK YOUR STACK →