restart_vpc · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What restart_vpc does on CloudStack MCP Server

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

Restarting a VPC is an Execute-category action because it runs/triggers an operation on cloud infrastructure that causes state changes but is reversible (unlike Destructive operations). The blast radius is high because restarting a VPC can interrupt service availability, cause temporary downtime, and affect all resources within that VPC.

From the tool's definition Tool name 'restart_vpc' and description 'Restart a Virtual Private Cloud' indicate an operational action that restarts infrastructure. This triggers external operations (stopping and restarting VPC resources) whose effects depend on which VPC is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restart_vpc Rate-limited

restart_vpc 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": {
    "restart_vpc": {
      "limits": [
        {
          "counter": "restart_vpc_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 restart_vpc

What does the restart_vpc tool do? +

Restart a Virtual Private Cloud. 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 restart_vpc? +

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

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

Can I rate-limit restart_vpc? +

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

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

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