reconnect_host
Reconnect disconnected host
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/reconnect-host.md
What reconnect_host does on CloudStack MCP Server
AI agents invoke reconnect_host 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 reconnect_host is rated High
Reconnecting a host triggers an external infrastructure operation (re-establishing the host connection in CloudStack). It doesn't simply read data, nor does it create/modify data in a traditional write sense, nor does it irreversibly destroy anything. It executes an operational action against a live infrastructure component. Misuse could cause disruption if applied to the wrong host, warranting medium severity.
From the tool's definition 'Reconnect disconnected host' — triggers an external operation to re-establish connection to a host
Attacks that exploit this kind of access
The rule that runs reconnect_host 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 reconnect_host, this is the rule to start with:
reconnect_host 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 reconnect_host call is checked against it from then on.
Questions about reconnect_host
Reconnect disconnected host. 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 reconnect_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.
reconnect_host 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 reconnect_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.
Set action: deny in the PolicyLayer policy for reconnect_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.
reconnect_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.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue