This record as markdown: /tools/gethosthewalrus-proxmox-mcp/reboot-container.md
What reboot_container does on Proxmox MCP Server
AI agents invoke reboot_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.
Why reboot_container is rated High
Rebooting a container is an external operational action that restarts a running service, causing temporary downtime. It is not purely destructive (no data loss) but it executes an operation with real infrastructure impact. Misuse could disrupt running workloads.
From the tool's definition 'Reboot a container' — triggers an external operation (reboot) on infrastructure
Attacks that exploit this kind of access
The rule that runs reboot_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 reboot_container, this is the rule to start with:
reboot_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every reboot_container call is checked against it from then on.
Questions about reboot_container
Reboot 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.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for reboot_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.
reboot_container is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the reboot_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.
Set action: deny in the PolicyLayer policy for reboot_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.
reboot_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.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue