This record as markdown: /tools/aapanel-mcp/project-delete.md
What project_delete does on Aapanel
AI agents call project_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 project_delete is rated Critical
This tool permanently removes a project and cannot be undone. Destructive operations represent the most severe category after Financial, and deletion has a significant blast radius in a hosting control panel context where projects may contain production configurations, databases, or deployed applications. High severity is appropriate given the irreversibility and potential business impact.
From the tool's definition Tool name 'project_delete' combined with description 'Delete a project' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs project_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 project_delete, this is the rule to start with:
project_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 project_delete call is checked against it from then on.
Questions about project_delete
Delete a project. 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 project_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.
project_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 project_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 project_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.
project_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