proxmox_clone_vm
A write tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-clone-vm.md
What proxmox_clone_vm does on MCP Proxmox Server
AI agents use proxmox_clone_vm to create or update resources in MCP Proxmox Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Proxmox Server environment.
Why proxmox_clone_vm is rated Medium
VM cloning is a write operation—it creates new compute resources and modifies the infrastructure state. While not immediately destructive (the original VM persists), it has high blast radius in a virtualization environment: an AI agent could rapidly spawn VMs consuming resources, incurring operational costs, or creating security/isolation concerns.
From the tool's definition Tool name 'proxmox_clone_vm' indicates VM cloning functionality. In Proxmox context, cloning creates a new virtual machine instance from an existing template or VM, which is a reversible write operation that modifies infrastructure state.
Attacks that exploit this kind of access
The rule that runs proxmox_clone_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_clone_vm, this is the rule to start with:
proxmox_clone_vm 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 MCP Proxmox Server, apply this rule, and every proxmox_clone_vm call is checked against it from then on.
Questions about proxmox_clone_vm
proxmox_clone_vm is a write tool on the MCP Proxmox Server MCP server. It is categorised as a Write tool in the MCP Proxmox Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_clone_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_clone_vm 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 proxmox_clone_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_clone_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_clone_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.
This server
Across the catalogue