controllers_power_cycle · CyPerf MCP Server MCP

WHAT IT DOES

What controllers_power_cycle does on CyPerf MCP Server

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

Power cycling compute nodes is a disruptive operation that restarts physical or virtual infrastructure. While it is technically recoverable (nodes can come back online), it causes service interruption, terminates active tests, and affects running workloads. It is an external operational trigger rather than a simple data write or destructive deletion, placing it firmly in Execute.

From the tool's definition Power cycle compute nodes

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

controllers_power_cycle Rate-limited

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

FAQ

Questions about controllers_power_cycle

What does the controllers_power_cycle tool do? +

[Controllers] Power cycle compute nodes. It is categorised as a Execute tool in the CyPerf 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 controllers_power_cycle? +

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

What risk level is controllers_power_cycle? +

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

Can I rate-limit controllers_power_cycle? +

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

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

controllers_power_cycle is provided by the CyPerf MCP Server MCP server (keysight/cyperf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.