stop_compose
A execute tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/stop-compose.md
What stop_compose does on 1Panel MCP Server
AI agents invoke stop_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 stop_compose is rated High
This tool triggers external operations (stopping Docker Compose services) whose effects depend on which compose configuration is targeted. While not permanently destructive or creating/modifying data, it executes commands that alter system state and can interrupt production workloads. This meets the Execute category (runs code/commands/triggers external operations).
From the tool's definition Tool name 'stop_compose' with description 'Stop compose' indicates execution of a Docker Compose command to halt running services.
Attacks that exploit this kind of access
The rule that runs stop_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 stop_compose, this is the rule to start with:
stop_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 stop_compose call is checked against it from then on.
Questions about stop_compose
stop_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 stop_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.
stop_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 stop_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 stop_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.
stop_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