stopall_node

Stop all VMs and containers on a node.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/stopall-node.md

WHAT IT DOES

What stopall_node does on Proxmox MCP Server

AI agents call stopall_node to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why stopall_node is rated Critical

Stopping all VMs and containers on a node is a massively disruptive, potentially irreversible action in terms of service continuity. It halts all running workloads on an entire node simultaneously, causing widespread outages. While it may not permanently delete data, abruptly stopping all guests can cause data corruption, crash running services, and requires significant recovery effort.

From the tool's definition Stop all VMs and containers on a node

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stopall_node 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 stopall_node, this is the rule to start with:

stopall_node Hidden

stopall_node is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "stopall_node"
  ]
}

RESTRICT 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 stopall_node call is checked against it from then on.

FAQ

Questions about stopall_node

What does the stopall_node tool do? +

Stop all VMs and containers on a node. It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on stopall_node? +

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

stopall_node is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit stopall_node? +

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

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

stopall_node 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 → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →