assign_virtual_machine
Assign virtual machine to account
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/assign-virtual-machine.md
What assign_virtual_machine does on CloudStack MCP Server
AI agents use assign_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 assign_virtual_machine is rated Medium
Assigning a virtual machine to a different account is a write operation that modifies resource metadata and ownership, with potential security implications if misused (e.g., transferring resources to unauthorized accounts). It is reversible, so not Destructive.
From the tool's definition Tool name is 'assign_virtual_machine' with description 'Assign virtual machine to account'. Assignment operations modify resource ownership/account associations, which is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs assign_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 assign_virtual_machine, this is the rule to start with:
assign_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 assign_virtual_machine call is checked against it from then on.
Questions about assign_virtual_machine
Assign virtual machine to account. 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 assign_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.
assign_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 assign_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 assign_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.
assign_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