start_compose
A execute tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/start-compose.md
What start_compose does on 1Panel MCP Server
AI agents invoke start_compose 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 start_compose is rated High
This tool triggers execution of Docker Compose configurations, which launches containerized applications and services. The effects are operational and depend entirely on what is defined in the compose file and runtime arguments. This is not merely a read (no data retrieval), write (no reversible data creation), or destructive action (nothing is permanently deleted).
From the tool's definition Tool name 'start_compose' paired with server description indicating 'Docker containers' and 'application deployment' management.
Attacks that exploit this kind of access
The rule that runs start_compose 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 start_compose, this is the rule to start with:
start_compose 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 start_compose call is checked against it from then on.
Questions about start_compose
start_compose 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 start_compose: 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.
start_compose 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 start_compose 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 start_compose. 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.
start_compose 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