reinstall_bare_metal_server
A execute tool on the Vultr MCP server.
This record as markdown: /tools/rsp2k-mcp-vultr/reinstall-bare-metal-server.md
What reinstall_bare_metal_server does on Vultr MCP
AI agents invoke reinstall_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 reinstall_bare_metal_server is rated High
Reinstalling a bare metal server wipes the OS and data on that server, triggering a destructive re-imaging operation. However, since it is a reinstall (potentially recoverable via backups or re-provisioning), it sits at the boundary of Execute/Destructive. Given the description is empty, confidence is moderate. The blast radius is high as it causes downtime and data loss on a physical server.
From the tool's definition Tool name: 'reinstall_bare_metal_server' — 'reinstall' implies re-imaging/wiping and reconfiguring a physical bare metal server
Attacks that exploit this kind of access
The rule that runs reinstall_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 reinstall_bare_metal_server, this is the rule to start with:
reinstall_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 reinstall_bare_metal_server call is checked against it from then on.
Questions about reinstall_bare_metal_server
reinstall_bare_metal_server is a execute tool on the Vultr MCP 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 reinstall_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.
reinstall_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 reinstall_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 reinstall_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.
reinstall_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