This record as markdown: /tools/aapanel-mcp/file-delete.md
What file_delete does on Aapanel
AI agents call file_delete to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why file_delete is rated Critical
This tool permanently removes files or directories without possibility of recovery (unless backup systems exist outside the tool's control). Unauthorized or incorrect use could destroy critical application files, configuration data, or user content. The ability to delete entire directories makes this a critical-severity risk with broad blast radius on a server management platform.
From the tool's definition Tool name is 'file_delete' with description 'Delete a file or directory on the server.' The terms 'delete' and 'directory' directly indicate irreversible data removal.
Attacks that exploit this kind of access
The rule that runs file_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_delete, this is the rule to start with:
file_delete 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 Aapanel, apply this rule, and every file_delete call is checked against it from then on.
Questions about file_delete
Delete a file or directory on the server. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for file_delete: 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 Aapanel. Nothing to install.
file_delete 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 file_delete 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 file_delete. 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.
file_delete is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue