start_router · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_router does on CloudStack MCP Server

AI agents invoke start_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 start_router needs a policy

This tool executes a command to change the operational state of a virtual router, affecting network traffic routing in the CloudStack infrastructure. While not destructive (the router can be stopped), it is an Execute-category action because it triggers an external operation with side effects.

From the tool's definition Tool name 'start_router' and description 'Start a virtual router' indicate execution of an operational command that triggers external effects on infrastructure—starting a network routing component whose state change depends on the argument (which router to…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_router Rate-limited

start_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": {
    "start_router": {
      "limits": [
        {
          "counter": "start_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 start_router

What does the start_router tool do? +

Start 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 start_router? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for start_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 start_router? +

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

Can I rate-limit start_router? +

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

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

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