power_action · KVMFleet MCP Server MCP: Risk & Policy

WHAT IT DOES

What power_action does on KVMFleet MCP Server

AI agents invoke power_action to trigger actions in KVMFleet 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 power_action needs a policy

While the description mentions destructive actions, the tool's primary function is to execute power commands whose effects are contingent on the specific argument passed. The tool triggers external operations (power state changes on devices) rather than permanently deleting data.

From the tool's definition Tool performs 'power action' operations including 'on, off, off_hard, cycle, reboot' which trigger external device state changes. Description explicitly notes 'Destructive actions (off, off_hard, cycle)' indicating irreversible effects on device state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

power_action Rate-limited

power_action 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": {
    "power_action": {
      "limits": [
        {
          "counter": "power_action_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 KVMFleet MCP Server, so you can run agents against it safely.

FAQ

Questions about power_action

What does the power_action tool do? +

Run a power action on a device: on, off, off_hard, cycle, reboot. Subject to org_admin/operator role, policy engine, and JIT access on the server. Destructive actions (off, off_hard, cycle) require. It is categorised as a Execute tool in the KVMFleet 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 power_action? +

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

What risk level is power_action? +

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

Can I rate-limit power_action? +

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

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

power_action is provided by the KVMFleet MCP Server MCP server (kvmfleet/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.