proxmox_restart_vm · Homelab MCP: Risk & Policy

WHAT IT DOES

What proxmox_restart_vm does on Homelab

AI agents invoke proxmox_restart_vm to trigger actions in Homelab. 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 IT NEEDS A POLICY

Why proxmox_restart_vm needs a policy

Restarting a VM or container is an Execute operation—it triggers an external system action with side effects that depend on user input. While not destructive (the VM persists), it disrupts service availability and could impact dependent systems or data in flight. The severity is high because an AI agent could restart critical infrastructure with a single misuse, causing significant downtime.

From the tool's definition Tool name 'proxmox_restart_vm' and description 'Restart a VM or LXC container by its VMID' indicates triggering an external operation (VM/container restart) whose effects depend on the VMID argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

proxmox_restart_vm Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Homelab, so you can run agents against it safely.

FAQ

Questions about proxmox_restart_vm

What does the proxmox_restart_vm tool do? +

Restart a VM or LXC container by its VMID. It is categorised as a Execute tool in the Homelab MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on proxmox_restart_vm? +

Register the Homelab MCP server in PolicyLayer and add a rule for proxmox_restart_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 Homelab. Nothing to install.

What risk level is proxmox_restart_vm? +

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

Can I rate-limit proxmox_restart_vm? +

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

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

proxmox_restart_vm is provided by the Homelab MCP server (nainounen/homelab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.