Create a snapshot of a VM
AI agents use create_vm_snapshot to create or update resources in Proxmox MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox MCP Server environment.
Creating a VM snapshot is a reversible Write operation that captures VM state. It creates new data but does not execute arbitrary code, delete resources, or commit financial transactions. The medium severity reflects that snapshots consume storage resources and could impact system capacity, but the operation is non-destructive and can be undone by deleting the snapshot (which would be a separate Destructive action).
From the tool's definition Tool name 'create_vm_snapshot' and description 'Create a snapshot of a VM' explicitly indicate creation of new data/state without deletion or irreversible modification.
Attacks that exploit this kind of access
Create a snapshot of a VM. It is categorised as a Write tool in the Proxmox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for create_vm_snapshot: 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.
create_vm_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_vm_snapshot 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 create_vm_snapshot. 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.
create_vm_snapshot is provided by the Proxmox MCP Server MCP server (ry-ops/proxmox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →