reset_vm
Hard reset a VM (like pressing the reset button).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/reset-vm.md
What reset_vm does on Proxmox MCP Server
AI agents invoke reset_vm to trigger actions in Proxmox MCP Server. 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 reset_vm is rated High
A hard reset forcibly restarts a VM without graceful shutdown, which can cause data loss or filesystem corruption in the guest OS. It is an irreversible disruptive action (any unsaved state is lost), but it does not delete or destroy the VM itself. This maps to Execute as it triggers an external hardware-level operation on infrastructure.
From the tool's definition Hard reset a VM (like pressing the reset button)
Attacks that exploit this kind of access
The rule that runs reset_vm safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_vm, this is the rule to start with:
reset_vm 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 Proxmox MCP Server, apply this rule, and every reset_vm call is checked against it from then on.
Questions about reset_vm
Hard reset a VM (like pressing the reset button). It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for reset_vm: 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 Proxmox MCP Server. Nothing to install.
reset_vm 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 reset_vm 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 reset_vm. 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.
reset_vm is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue