create_container
A execute tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/create-container.md
What create_container does on 1Panel MCP Server
AI agents invoke create_container to trigger actions in 1Panel 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 create_container is rated High
Creating a container launches a new runtime environment that can execute arbitrary code/processes. While it is technically a 'write' (creating a resource), the act of instantiating and running a container constitutes an external execution operation with significant blast radius — a misused container could run malicious processes, consume resources, or serve as a pivot point.
From the tool's definition Tool name 'create_container' and description 'Create container' indicate spawning a new Docker container, which is an external operation that executes a containerized workload
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 1Panel 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 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 1Panel 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 execute tool on the 1Panel MCP Server MCP server. It is categorised as a Execute tool in the 1Panel MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the 1Panel 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 1Panel MCP Server. Nothing to install.
create_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 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 1Panel MCP Server MCP server (eaveluo/1panel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 1Panel MCP Server, and thousands of servers like it.
Across the catalogue