clean_container_log

A destructive tool on the 1Panel MCP server.

SERVER1Panel MCP Server SOURCEeaveluo/1panel-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eaveluo-1panel-mcp/clean-container-log.md

WHAT IT DOES

What clean_container_log does on 1Panel MCP Server

AI agents call clean_container_log 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.

RISK

Why clean_container_log is rated Critical

Cleaning container logs permanently removes log data. This is an irreversible operation (logs cannot be recovered once cleaned), making it Destructive. The blast radius is medium since it only affects log files, not running services or application data, but the loss of logs can impact debugging, auditing, and compliance.

From the tool's definition 'Clean container log' — cleaning logs is an irreversible deletion of log data that cannot be undone

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs clean_container_log 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 clean_container_log, this is the rule to start with:

clean_container_log Hidden

clean_container_log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "clean_container_log"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 1Panel MCP Server, apply this rule, and every clean_container_log call is checked against it from then on.

FAQ

Questions about clean_container_log

What does the clean_container_log tool do? +

clean_container_log 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.

How do I enforce a policy on clean_container_log? +

Register the 1Panel MCP Server MCP server in PolicyLayer and add a rule for clean_container_log: 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.

What risk level is clean_container_log? +

clean_container_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit clean_container_log? +

Yes. Add a rate_limit block to the clean_container_log 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.

How do I block clean_container_log completely? +

Set action: deny in the PolicyLayer policy for clean_container_log. 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.

What MCP server provides clean_container_log? +

clean_container_log 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.

KEEP EXPLORING

More on 1Panel MCP Server, and thousands of servers like it.

This server

All 286 1Panel MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →