stop_router · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_router does on CloudStack MCP Server

AI agents invoke stop_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 stop_router needs a policy

Stopping a router is an operational execution that affects live infrastructure and potentially disrupts network connectivity for dependent systems. However, it is not destructive (the router can be restarted) and is reversible. It matches the Execute category as it triggers an external operation whose effects depend on infrastructure arguments.

From the tool's definition Tool name is 'stop_router' and description states 'Stop a virtual router'. This performs a network control action on infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_router Rate-limited

stop_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": {
    "stop_router": {
      "limits": [
        {
          "counter": "stop_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 stop_router

What does the stop_router tool do? +

Stop 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 stop_router? +

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

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

Can I rate-limit stop_router? +

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

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

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