This record as markdown: /tools/eaveluo-1panel-mcp/delete-file.md
What delete_file does on 1Panel MCP Server
AI agents call delete_file 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 delete_file is rated Critical
Deleting files or directories cannot be undone and represents permanent data loss. In the context of a server management tool with infrastructure access, this poses critical risk if invoked on sensitive system files, configurations, or user data. The blast radius is maximum — an AI agent misusing this could destroy entire applications, databases, or system integrity.
From the tool's definition Tool name 'delete_file' with description 'Delete file or directory' explicitly performs irreversible removal of filesystem objects.
Attacks that exploit this kind of access
The rule that runs delete_file 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 delete_file, this is the rule to start with:
delete_file 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 delete_file call is checked against it from then on.
Questions about delete_file
Delete file or directory. 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 delete_file: 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.
delete_file 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 delete_file 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 delete_file. 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.
delete_file 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