reboot

Reboot an instance.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rsp2k-mcp-vultr/reboot.md

WHAT IT DOES

What reboot does on Vultr MCP

AI agents invoke reboot to trigger actions in Vultr MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why reboot is rated High

Rebooting an instance is an external operation that interrupts running workloads, potentially causing downtime and service disruption. It is not a simple read or write, nor is it destructive (data is preserved), but it executes an action with significant operational impact.

From the tool's definition 'Reboot an instance' — triggers an external operation (restart) on a cloud compute instance

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs reboot 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 reboot, this is the rule to start with:

reboot Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every reboot call is checked against it from then on.

FAQ

Questions about reboot

What does the reboot tool do? +

Reboot an instance. 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? +

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

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

Can I rate-limit reboot? +

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

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

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

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr tools → High-risk tools on this server →

Across the catalogue

reboot_device on Android Forensics ADB MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →