declare_host_as_degraded
A execute tool on the CloudStack MCP server.
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/declare-host-as-degraded.md
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 declare_host_as_degraded is rated High
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
The rule that runs declare_host_as_degraded 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 declare_host_as_degraded, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every declare_host_as_degraded call is checked against it from then on.
Questions about declare_host_as_degraded
declare_host_as_degraded is a execute tool on the CloudStack MCP Server MCP server. 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.
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.
declare_host_as_degraded is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue