recover_virtual_machine

Recover a destroyed virtual machine

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

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/mozg31337-cloudstack-mcp-server/recover-virtual-machine.md

WHAT IT DOES

What recover_virtual_machine does on CloudStack MCP Server

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

RISK

Why recover_virtual_machine is rated Medium

Recovering a destroyed VM is a reversible write/restore operation that brings back a resource. It is not itself destructive (no data is deleted), not financial, and not just a read.

From the tool's definition 'Recover a destroyed virtual machine' — restores a previously destroyed VM back to an operational state

Attacks that exploit this kind of access

RECOMMENDED RULE

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

recover_virtual_machine Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "recover_virtual_machine": {
      "limits": [
        {
          "counter": "recover_virtual_machine_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 CloudStack MCP Server, apply this rule, and every recover_virtual_machine call is checked against it from then on.

FAQ

Questions about recover_virtual_machine

What does the recover_virtual_machine tool do? +

Recover a destroyed virtual machine. 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.

How do I enforce a policy on recover_virtual_machine? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for recover_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.

What risk level is recover_virtual_machine? +

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

Can I rate-limit recover_virtual_machine? +

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

How do I block recover_virtual_machine completely? +

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

What MCP server provides recover_virtual_machine? +

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

KEEP EXPLORING

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

This server

All 442 CloudStack MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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