resume_container
Resume a suspended container.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/resume-container.md
What resume_container does on Proxmox MCP Server
AI agents invoke resume_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 resume_container is rated High
Resuming a suspended container triggers an external operational state change on infrastructure — it causes a container to transition from suspended to running state. This is an Execute-level action as it triggers an external operation with real effects, but it is not destructive (it does not delete or overwrite data) nor financial.
From the tool's definition Resume a suspended container
Attacks that exploit this kind of access
The rule that runs resume_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 resume_container, this is the rule to start with:
resume_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 resume_container call is checked against it from then on.
Questions about resume_container
Resume a suspended 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 resume_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.
resume_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 resume_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 resume_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.
resume_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