convert_vm_to_template
Convert a VM into a template (irreversible).
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/convert-vm-to-template.md
What convert_vm_to_template does on Proxmox MCP Server
AI agents call convert_vm_to_template to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why convert_vm_to_template is rated Critical
Converting a VM to a template is an irreversible transformation that fundamentally changes the nature of the resource and prevents it from being used as an active VM. While not a deletion per se, it destroys the VM's functionality in its original form without a recovery path.
From the tool's definition Tool description explicitly states 'Convert a VM into a template (irreversible).' The word 'irreversible' confirms this is a destructive operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs convert_vm_to_template 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 convert_vm_to_template, this is the rule to start with:
convert_vm_to_template is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every convert_vm_to_template call is checked against it from then on.
Questions about convert_vm_to_template
Convert a VM into a template (irreversible). It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for convert_vm_to_template: 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.
convert_vm_to_template is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the convert_vm_to_template 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 convert_vm_to_template. 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.
convert_vm_to_template 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.
Across the catalogue