create_container_snapshot
Create a snapshot of a container.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/create-container-snapshot.md
What create_container_snapshot does on Proxmox MCP Server
AI agents use create_container_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.
Why create_container_snapshot is rated Medium
Creating a snapshot is a write operation that creates new backup data but does not irreversibly delete or destroy anything. It modifies the infrastructure state by adding a new snapshot resource. The blast radius is medium because snapshots consume storage and could impact performance or storage availability if created excessively, but the operation itself is reversible and non-destructive.
From the tool's definition Tool creates a snapshot of a container, which is a new point-in-time copy of the container's filesystem and state. The description explicitly states 'Create a snapshot', indicating data modification and creation of a new resource.
Attacks that exploit this kind of access
The rule that runs create_container_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_container_snapshot, this is the rule to start with:
create_container_snapshot 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every create_container_snapshot call is checked against it from then on.
Questions about create_container_snapshot
Create a snapshot of a container. 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_container_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_container_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_container_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_container_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_container_snapshot is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
This server
Across the catalogue