shutdown_instance · Verda Cloud MCP Server MCP

WHAT IT DOES

What shutdown_instance does on Verda Cloud MCP Server

AI agents invoke shutdown_instance to trigger actions in Verda Cloud 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 shutdown_instance needs a policy

Shutting down a running instance is an external operation with significant operational impact (stopping workloads, interrupting services). It is not destructive since the instance can be restarted, but it triggers an external state change on infrastructure, making it Execute. Misuse by an AI agent could halt critical GPU workloads, hence high severity.

From the tool's definition Shutdown a running instance (can be restarted later)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shutdown_instance Rate-limited

shutdown_instance 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": {
    "shutdown_instance": {
      "limits": [
        {
          "counter": "shutdown_instance_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 Verda Cloud MCP Server, so you can run agents against it safely.

FAQ

Questions about shutdown_instance

What does the shutdown_instance tool do? +

Shutdown a running instance (can be restarted later). It is categorised as a Execute tool in the Verda Cloud 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 shutdown_instance? +

Register the Verda Cloud MCP Server MCP server in PolicyLayer and add a rule for shutdown_instance: 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 Verda Cloud MCP Server. Nothing to install.

What risk level is shutdown_instance? +

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

Can I rate-limit shutdown_instance? +

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

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

shutdown_instance is provided by the Verda Cloud MCP Server MCP server (sniper35/verda-cloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.