copy_virtual_machine
Copy virtual machine to another zone
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/copy-virtual-machine.md
What copy_virtual_machine does on CloudStack MCP Server
AI agents use copy_virtual_machine to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.
Why copy_virtual_machine is rated Medium
Copying a VM to another zone creates a new VM instance (Write), but does not delete the original. However, this can have significant resource and cost implications across infrastructure zones, raising the severity to high. It is not Financial (no direct monetary transaction) nor Destructive (original is preserved).
From the tool's definition 'Copy virtual machine to another zone' - copying creates a new resource in another zone without destroying the original
Attacks that exploit this kind of access
The rule that runs copy_virtual_machine safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For copy_virtual_machine, this is the rule to start with:
copy_virtual_machine 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 CloudStack MCP Server, apply this rule, and every copy_virtual_machine call is checked against it from then on.
Questions about copy_virtual_machine
Copy virtual machine to another zone. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for copy_virtual_machine: 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 CloudStack MCP Server. Nothing to install.
copy_virtual_machine 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 copy_virtual_machine 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 copy_virtual_machine. 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.
copy_virtual_machine is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CloudStack MCP Server, and thousands of servers like it.
This server
Across the catalogue