stop_vps

Stop a running VPS

SERVER20i MCP Server SOURCEcbrown35/20i-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cbrown35-20i-mcp/stop-vps.md

WHAT IT DOES

What stop_vps does on 20i MCP Server

AI agents invoke stop_vps to trigger actions in 20i 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.

RISK

Why stop_vps is rated High

Stopping a VPS is an Execute-class action because it triggers an external operation (VPS shutdown) whose effects depend on arguments (which VPS to stop). While the action is reversible (VPS can be restarted), it immediately disrupts service availability and causes operational impact.

From the tool's definition Tool name 'stop_vps' and description 'Stop a running VPS' indicate execution of an infrastructure control operation that terminates a virtual private server.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_vps safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_vps, this is the rule to start with:

stop_vps Rate-limited

stop_vps 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_vps": {
      "limits": [
        {
          "counter": "stop_vps_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every stop_vps call is checked against it from then on.

FAQ

Questions about stop_vps

What does the stop_vps tool do? +

Stop a running VPS. It is categorised as a Execute tool in the 20i 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_vps? +

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

What risk level is stop_vps? +

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

Can I rate-limit stop_vps? +

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

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

stop_vps is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →