disable_vm_ha

Disable high availability for 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/disable-vm-ha.md

WHAT IT DOES

What disable_vm_ha does on CloudStack MCP Server

AI agents use disable_vm_ha 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 disable_vm_ha is rated Medium

This tool modifies VM settings by disabling high availability, which is a state change that affects infrastructure resilience but is reversible. It does not delete data, execute arbitrary commands, or move money. It fits the Write category as it updates configuration.

From the tool's definition Tool name is 'disable_vm_ha' and description states 'Disable high availability for virtual machine'. This modifies the HA configuration of a VM, which is a reversible configuration change (HA can be re-enabled).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

disable_vm_ha Rate-limited

disable_vm_ha 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": {
    "disable_vm_ha": {
      "limits": [
        {
          "counter": "disable_vm_ha_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 disable_vm_ha call is checked against it from then on.

FAQ

Questions about disable_vm_ha

What does the disable_vm_ha tool do? +

Disable high availability for 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 disable_vm_ha? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for disable_vm_ha: 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 disable_vm_ha? +

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

Can I rate-limit disable_vm_ha? +

Yes. Add a rate_limit block to the disable_vm_ha 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 disable_vm_ha completely? +

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

disable_vm_ha 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 →