shutdown_container

Gracefully shut down a container.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-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/gethosthewalrus-proxmox-mcp/shutdown-container.md

WHAT IT DOES

What shutdown_container does on Proxmox MCP Server

AI agents invoke shutdown_container to trigger actions in Proxmox 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 shutdown_container is rated High

Shutting down a container triggers an external operation that stops a running workload. While potentially reversible (the container can be restarted), the act of shutting down is an execution of an operational command with significant impact — it interrupts services and workloads running inside the container.

From the tool's definition Gracefully shut down a container

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs shutdown_container safely

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

shutdown_container Rate-limited

shutdown_container 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_container": {
      "limits": [
        {
          "counter": "shutdown_container_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 Proxmox MCP Server, apply this rule, and every shutdown_container call is checked against it from then on.

FAQ

Questions about shutdown_container

What does the shutdown_container tool do? +

Gracefully shut down a container. It is categorised as a Execute tool in the Proxmox 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_container? +

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

What risk level is shutdown_container? +

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

Can I rate-limit shutdown_container? +

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

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

shutdown_container is provided by the Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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