clone_vm

A write tool on the Proxmox MCP server.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/clone-vm.md

WHAT IT DOES

What clone_vm does on Proxmox MCP Server

AI agents use clone_vm 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.

RISK

Why clone_vm is rated Medium

Based on the tool name 'clone_vm', this tool most likely creates a clone (copy) of a virtual machine, which is a Write operation as it creates new data/resources. In the context of Proxmox VE infrastructure management, cloning a VM is reversible (the clone can be deleted), placing it in Write rather than Destructive.

From the tool's definition Tool name 'clone_vm'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clone_vm 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 clone_vm, this is the rule to start with:

clone_vm Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "clone_vm": {
      "limits": [
        {
          "counter": "clone_vm_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every clone_vm call is checked against it from then on.

FAQ

Questions about clone_vm

What does the clone_vm tool do? +

clone_vm is a write tool on the Proxmox MCP Server MCP server. 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.

How do I enforce a policy on clone_vm? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for 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 Proxmox MCP Server. Nothing to install.

What risk level is clone_vm? +

clone_vm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit clone_vm? +

Yes. Add a rate_limit block to the 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.

How do I block clone_vm completely? +

Set action: deny in the PolicyLayer policy for 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.

What MCP server provides clone_vm? +

clone_vm 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.

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →