reboot_router · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What reboot_router does on CloudStack MCP Server

AI agents invoke reboot_router 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 IT NEEDS A POLICY

Why reboot_router needs a policy

Rebooting a virtual router causes a service interruption for all traffic routed through it, affecting potentially many dependent workloads. It is an execution of an external infrastructure operation, not a simple data read/write, and while the router comes back online (not permanently destroyed), the disruption can be severe. Falls under Execute as it triggers an external operation with significant blast radius.

From the tool's definition 'Reboot a virtual router' — triggers an external operation (rebooting infrastructure) that disrupts network routing services

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_router Rate-limited

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

FAQ

Questions about reboot_router

What does the reboot_router tool do? +

Reboot a virtual router. 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.

How do I enforce a policy on reboot_router? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for reboot_router: 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.

What risk level is reboot_router? +

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

Can I rate-limit reboot_router? +

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

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

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