This record as markdown: /tools/rsp2k-mcp-vultr/reboot-bare-metal-server.md
What reboot_bare_metal_server does on Vultr MCP
AI agents invoke reboot_bare_metal_server 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.
Why reboot_bare_metal_server is rated High
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
Attacks that exploit this kind of access
The rule that runs reboot_bare_metal_server 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_bare_metal_server, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every reboot_bare_metal_server call is checked against it from then on.
Questions about reboot_bare_metal_server
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.
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.
reboot_bare_metal_server is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on Vultr, and thousands of servers like it.
Across the catalogue