remove_compose
A destructive tool on the 1Panel MCP server.
This record as markdown: /tools/eaveluo-1panel-mcp/remove-compose.md
What remove_compose does on 1Panel MCP Server
AI agents call remove_compose to permanently remove resources in 1Panel MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why remove_compose is rated Critical
This tool irreversibly deletes Docker Compose resources. Once removed, the compose configuration and associated containers/services are gone. While potentially recoverable from backups, the action itself is non-idempotent and destructive. The high severity reflects that removing compose stacks can take down critical applications and services in production environments.
From the tool's definition Tool name 'remove_compose' combined with server context of Docker and application deployment management indicates irreversible deletion of Docker Compose configurations/services.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_compose, this is the rule to start with:
remove_compose is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every remove_compose call is checked against it from then on.
Questions about remove_compose
remove_compose is a destructive tool on the 1Panel MCP Server MCP server. It is categorised as a Destructive tool in the 1Panel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for remove_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.
remove_compose is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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