This record as markdown: /tools/aapanel-mcp/site-delete-domain.md
What site_delete_domain does on Aapanel
AI agents call site_delete_domain 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 site_delete_domain is rated Critical
This operation irreversibly removes a domain association, which cannot be easily undone without manual reconfiguration. While not a complete data wipe, domain deletion from a site can disrupt service accessibility and DNS bindings. The 'delete' verb and 'remove' description indicate destructive intent.
From the tool's definition Tool name 'site_delete_domain' combined with description 'Remove a domain from a site' indicates irreversible deletion of a domain binding from a site configuration.
Attacks that exploit this kind of access
The rule that runs site_delete_domain 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 site_delete_domain, this is the rule to start with:
site_delete_domain 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 site_delete_domain call is checked against it from then on.
Questions about site_delete_domain
Remove a domain from a site. 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 site_delete_domain: 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.
site_delete_domain 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 site_delete_domain 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 site_delete_domain. 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.
site_delete_domain 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