shutdown_vm

A destructive tool on the Proxmox MCP server.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/shutdown-vm.md

WHAT IT DOES

What shutdown_vm does on Proxmox MCP Server

AI agents call shutdown_vm to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why shutdown_vm is rated Critical

Shutting down a VM interrupts running workloads and may cause data loss or service disruption. While a shutdown can be reversed by starting the VM again, the immediate impact of stopping a running VM is significant. The sibling tool 'bulk_shutdown_guests' on the same server further suggests this is a disruptive power-state action.

From the tool's definition Tool name 'shutdown_vm'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

shutdown_vm Hidden

shutdown_vm is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "shutdown_vm"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about shutdown_vm

What does the shutdown_vm tool do? +

shutdown_vm is a destructive tool on the Proxmox MCP Server MCP server. It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on shutdown_vm? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for shutdown_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.

What risk level is shutdown_vm? +

shutdown_vm is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit shutdown_vm? +

Yes. Add a rate_limit block to the shutdown_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.

How do I block shutdown_vm completely? +

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

What MCP server provides shutdown_vm? +

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

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →