disable_ha_for_host · CloudStack MCP Server MCP

WHAT IT DOES

What disable_ha_for_host does on CloudStack MCP Server

AI agents use disable_ha_for_host 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 IT NEEDS A POLICY

Why disable_ha_for_host needs a policy

Disabling HA (High Availability) for a host is a reversible configuration modification that changes the operational state of infrastructure. While it impacts availability and resilience, it is not destructive (the host and its configuration remain intact and can be re-enabled), not financial, and not arbitrary code execution. It is a Write operation because it modifies infrastructure configuration state.

From the tool's definition Tool name: 'disable_ha_for_host' - the verb 'disable' indicates modification of host configuration state. Description: 'Disable HA for host' confirms this is a configuration change operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

disable_ha_for_host Rate-limited

disable_ha_for_host 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_ha_for_host": {
      "limits": [
        {
          "counter": "disable_ha_for_host_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about disable_ha_for_host

What does the disable_ha_for_host tool do? +

Disable HA for host. 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_ha_for_host? +

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

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

Can I rate-limit disable_ha_for_host? +

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

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

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