vm_clone
Clone an existing VM, creating a copy with a new name.
This record as markdown: /tools/spranab-truenas-mcp/vm-clone.md
What vm_clone does on Truenas
AI agents use vm_clone to create or update resources in Truenas, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Truenas environment.
Why vm_clone is rated Medium
Cloning a VM creates a new copy of an existing virtual machine, which is a reversible write/create operation. It does not delete or overwrite existing data, nor does it execute arbitrary code. However, it can consume significant storage and compute resources, giving it a high severity if misused by an AI agent creating many clones.
From the tool's definition Clone an existing VM, creating a copy with a new name
Attacks that exploit this kind of access
The rule that runs vm_clone safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_clone, this is the rule to start with:
vm_clone 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 Truenas, apply this rule, and every vm_clone call is checked against it from then on.
Questions about vm_clone
Clone an existing VM, creating a copy with a new name. It is categorised as a Write tool in the Truenas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Truenas MCP server in PolicyLayer and add a rule for vm_clone: 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 Truenas. Nothing to install.
vm_clone 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 vm_clone 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 vm_clone. 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.
vm_clone is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
This server
Across the catalogue