assign_vm_to_backup_offering
Assign virtual machine to backup offering
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/assign-vm-to-backup-offering.md
What assign_vm_to_backup_offering does on CloudStack MCP Server
AI agents use assign_vm_to_backup_offering 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_vm_to_backup_offering is rated Medium
This tool modifies VM state by changing its backup offering association. It is Write-category because it updates existing infrastructure configuration reversibly (the assignment can be changed or removed). Severity is high because incorrect backup offering assignment could disable backups or assign to wrong service tier, affecting data protection posture and potential compliance.
From the tool's definition 'Assign virtual machine to backup offering' modifies VM configuration by associating it with a backup service offering, which is a reversible state change to infrastructure.
Attacks that exploit this kind of access
The rule that runs assign_vm_to_backup_offering 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_vm_to_backup_offering, this is the rule to start with:
assign_vm_to_backup_offering 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_vm_to_backup_offering call is checked against it from then on.
Questions about assign_vm_to_backup_offering
Assign virtual machine to backup offering. 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_vm_to_backup_offering: 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_vm_to_backup_offering 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_vm_to_backup_offering 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_vm_to_backup_offering. 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_vm_to_backup_offering 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