This record as markdown: /tools/aapanel-mcp/waf-delete-rule.md
What waf_delete_rule does on Aapanel
AI agents call waf_delete_rule 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 waf_delete_rule is rated Critical
This tool permanently removes a WAF (Web Application Firewall) rule, which is a security control. Deletion is irreversible and directly impacts the security posture of the system. While not as severe as deleting entire databases, removing security rules creates exposure to attacks that the rule previously prevented.
From the tool's definition Tool name contains 'delete' and description states 'Delete a WAF rule by ID.' The action is irreversible—removing a WAF security rule cannot be undone without manual recreation.
Attacks that exploit this kind of access
The rule that runs waf_delete_rule 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 waf_delete_rule, this is the rule to start with:
waf_delete_rule 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 waf_delete_rule call is checked against it from then on.
Questions about waf_delete_rule
Delete a WAF rule by ID. 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 waf_delete_rule: 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.
waf_delete_rule 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 waf_delete_rule 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 waf_delete_rule. 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.
waf_delete_rule 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