shutdown_digitalocean_droplet · Cloud Manage MCP Server MCP

WHAT IT DOES

What shutdown_digitalocean_droplet does on Cloud Manage MCP Server

AI agents invoke shutdown_digitalocean_droplet to trigger actions in Cloud Manage 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_digitalocean_droplet needs a policy

Shutting down a cloud server is an external operational action that stops a running instance. While not permanently destructive (the droplet still exists and can be restarted), it triggers a significant external side effect — halting services and workloads on the droplet. This falls under Execute (triggering external operations).

From the tool's definition shutdown_digitalocean_droplet — '优雅关闭DigitalOcean Droplet' (gracefully shut down a DigitalOcean Droplet)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shutdown_digitalocean_droplet Rate-limited

shutdown_digitalocean_droplet 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_digitalocean_droplet": {
      "limits": [
        {
          "counter": "shutdown_digitalocean_droplet_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 Cloud Manage MCP Server, so you can run agents against it safely.

FAQ

Questions about shutdown_digitalocean_droplet

What does the shutdown_digitalocean_droplet tool do? +

优雅关闭DigitalOcean Droplet（需要三次确认）. It is categorised as a Execute tool in the Cloud Manage 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_digitalocean_droplet? +

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

What risk level is shutdown_digitalocean_droplet? +

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

Can I rate-limit shutdown_digitalocean_droplet? +

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

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

shutdown_digitalocean_droplet is provided by the Cloud Manage MCP Server MCP server (rainhan99/cloud_manage_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.