pve_set_vm_config · Proxmox MCP: Risk & Policy

WHAT IT DOES

What pve_set_vm_config does on Proxmox

AI agents use pve_set_vm_config to create or update resources in Proxmox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox environment.

WHY IT NEEDS A POLICY

Why pve_set_vm_config needs a policy

This tool modifies VM/container configuration properties, which is a Write operation—creating or updating data reversibly. While it affects system state, the changes are not destructive (can be reverted), not financial, and do not execute arbitrary code. The 'confirm=true' gate provides some safety. Severity is high because misconfiguration of VMs could impact availability or security, affecting multiple systems.

From the tool's definition 'Update VM/container config' with 'confirm=true' requirement indicates reversible modification of virtual machine configuration settings without data destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pve_set_vm_config Rate-limited

pve_set_vm_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pve_set_vm_config": {
      "limits": [
        {
          "counter": "pve_set_vm_config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about pve_set_vm_config

What does the pve_set_vm_config tool do? +

Update VM/container config. Requires confirm=true. It is categorised as a Write tool in the Proxmox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on pve_set_vm_config? +

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

What risk level is pve_set_vm_config? +

pve_set_vm_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pve_set_vm_config? +

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

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

pve_set_vm_config is provided by the Proxmox MCP server (plgonzalezrx8/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.