declare_host_as_degraded · CloudStack MCP Server MCP

WHAT IT DOES

What declare_host_as_degraded does on CloudStack MCP Server

AI agents invoke declare_host_as_degraded to trigger actions in CloudStack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why declare_host_as_degraded needs a policy

Declaring a host as degraded changes its operational status, which can trigger workload migrations, prevent new VM scheduling, and affect production infrastructure. This is an Execute-level action (triggering external operations with significant side effects) rather than Destructive since it doesn't irreversibly delete data, but it carries high severity due to potential disruption of infrastructure services and…

From the tool's definition 'Declare host as degraded' — changes the operational state/status of a host in CloudStack infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

declare_host_as_degraded Rate-limited

declare_host_as_degraded stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "declare_host_as_degraded": {
      "limits": [
        {
          "counter": "declare_host_as_degraded_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 declare_host_as_degraded

What does the declare_host_as_degraded tool do? +

Declare host as degraded. It is categorised as a Execute tool in the CloudStack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on declare_host_as_degraded? +

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

declare_host_as_degraded is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit declare_host_as_degraded? +

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

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

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