controllers_reboot_port · CyPerf MCP Server MCP

WHAT IT DOES

What controllers_reboot_port does on CyPerf MCP Server

AI agents invoke controllers_reboot_port 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_reboot_port needs a policy

Rebooting a port on a controller triggers an external hardware/network operation that disrupts active traffic flows and test sessions. It is not a simple data read or write — it executes a stateful hardware action. While not permanently destructive, it can interrupt ongoing tests and affect network availability, warranting a high severity rating.

From the tool's definition Reboot a port on a controller

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

controllers_reboot_port Rate-limited

controllers_reboot_port 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_reboot_port": {
      "limits": [
        {
          "counter": "controllers_reboot_port_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_reboot_port

What does the controllers_reboot_port tool do? +

[Controllers] Reboot a port on a controller. 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_reboot_port? +

Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for controllers_reboot_port: 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_reboot_port? +

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

Can I rate-limit controllers_reboot_port? +

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

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

controllers_reboot_port 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.