manage_instance_power · Cloud Manage MCP Server MCP

WHAT IT DOES

What manage_instance_power does on Cloud Manage MCP Server

AI agents invoke manage_instance_power to trigger actions in Cloud Manage 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 manage_instance_power needs a policy

Power management of cloud instances (power on, power off, reboot, shutdown) triggers external operations on live infrastructure. The description is empty, but the server description explicitly mentions 'power management' as a capability, and the tool name clearly indicates controlling instance power state. This is an Execute-category action with high severity since misuse could take down production servers.

From the tool's definition Tool name 'manage_instance_power' in context of a server that performs 'power management' operations on cloud instances (DigitalOcean droplets and others).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_instance_power Rate-limited

manage_instance_power 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": {
    "manage_instance_power": {
      "limits": [
        {
          "counter": "manage_instance_power_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 Cloud Manage MCP Server, so you can run agents against it safely.

FAQ

Questions about manage_instance_power

What does the manage_instance_power tool do? +

manage_instance_power. It is categorised as a Execute tool in the Cloud Manage 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 manage_instance_power? +

Register the Cloud Manage MCP Server MCP server in PolicyLayer and add a rule for manage_instance_power: 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 Cloud Manage MCP Server. Nothing to install.

What risk level is manage_instance_power? +

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

Can I rate-limit manage_instance_power? +

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

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

manage_instance_power is provided by the Cloud Manage MCP Server MCP server (rainhan99/cloud_manage_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.