suspend_container
Suspend (freeze) a container.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/suspend-container.md
What suspend_container does on Proxmox MCP Server
AI agents invoke suspend_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 suspend_container is rated High
Suspending/freezing a container is an external operational action that changes the runtime state of infrastructure. It is not a simple read or write of data, but an execution of a lifecycle command. While it can be reversed (resumed), the act of freezing a container disrupts running workloads and could cause service outages, making it high severity if misused by an AI agent.
From the tool's definition 'Suspend (freeze) a container' — triggers an operational state change on a running container in the Proxmox VE infrastructure.
Attacks that exploit this kind of access
The rule that runs suspend_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 suspend_container, this is the rule to start with:
suspend_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 suspend_container call is checked against it from then on.
Questions about suspend_container
Suspend (freeze) 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 suspend_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.
suspend_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 suspend_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 suspend_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.
suspend_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