proxmox_start_vm
A execute tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-start-vm.md
What proxmox_start_vm does on MCP Proxmox Server
AI agents invoke proxmox_start_vm to trigger actions in MCP Proxmox 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 proxmox_start_vm is rated High
Starting a VM is an Execute action: it runs/triggers an operation on external infrastructure whose effects depend on arguments (which VM). While not destructive or financial, it has high blast radius in a cloud environment—an AI agent could spin up expensive compute resources or start VMs affecting production workloads.
From the tool's definition Tool name 'proxmox_start_vm' combined with server description indicating 'VM/LXC lifecycle operations' and 'full access to Proxmox API functionality' shows this starts virtual machines—a state-changing operation that triggers external compute infrastructure.
Attacks that exploit this kind of access
The rule that runs proxmox_start_vm safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_start_vm, this is the rule to start with:
proxmox_start_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 MCP Proxmox Server, apply this rule, and every proxmox_start_vm call is checked against it from then on.
Questions about proxmox_start_vm
proxmox_start_vm is a execute tool on the MCP Proxmox Server MCP server. It is categorised as a Execute tool in the MCP Proxmox Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_start_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 MCP Proxmox Server. Nothing to install.
proxmox_start_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 proxmox_start_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 proxmox_start_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.
proxmox_start_vm is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
Across the catalogue