create_container
A write tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/create-container.md
What create_container does on Proxmox MCP Server
AI agents use create_container to create or update resources in Proxmox MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Proxmox MCP Server environment.
Why create_container is rated Medium
Creating a container is a reversible write operation that allocates and configures compute resources. While not destructive (cannot be undone irreversibly at creation time), it modifies infrastructure state and could consume significant resources or disrupt systems if misused by an agent. Not Execute-level because container creation is a direct resource allocation, not arbitrary code execution.
From the tool's definition Tool name 'create_container' in Proxmox MCP Server context indicates creation of container resources. Description is empty, reducing certainty, but the Proxmox domain (infrastructure/virtualization management) and sibling tools (clone_container,…
Attacks that exploit this kind of access
The rule that runs create_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 create_container, this is the rule to start with:
create_container stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 create_container call is checked against it from then on.
Questions about create_container
create_container is a write tool on the Proxmox MCP Server MCP server. It is categorised as a Write tool in the Proxmox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for create_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.
create_container is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue