Create a snapshot of a VM
AI agents use pve_create_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.
Snapshots are a form of state preservation that can be created, managed, and deleted reversibly. While they consume storage and can impact system performance, they do not irreversibly destroy data (like delete/drop operations) nor move financial resources. They represent a modification/creation of infrastructure state, placing this firmly in the Write category.
From the tool's definition Tool creates a snapshot of a VM, which is a reversible operation that persists new data (the snapshot state) without destruction. The description explicitly states 'Create a snapshot.'
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 pve_create_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.
pve_create_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 pve_create_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 pve_create_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.
pve_create_snapshot is provided by the Proxmox MCP Server MCP server (mjrestivo16/mcp-proxmox). 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 →