AI agents call delete_email_filter to permanently remove resources in cPanel MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Email filters are configuration that, once deleted, cannot be automatically recovered without manual reconfiguration. Deletion is irreversible and results in loss of the filter rules and their protective/organizational effects. An AI agent misusing this tool could delete critical spam filters, security rules, or user-defined filters that protect email delivery or organization.
From the tool's definition Tool name explicitly states 'delete_email_filter' and description confirms 'Delete an email filter'. This is a destructive operation that irreversibly removes email filtering configuration.
Documented attack patterns abuse exactly the kind of access delete_email_filter gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_email_filter:
{
"version": "1",
"default": "deny",
"hide": [
"delete_email_filter"
]
}delete_email_filter disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete an email filter. It is categorised as a Destructive tool in the cPanel MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for delete_email_filter: 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 cPanel MCP Server. Nothing to install.
delete_email_filter 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_email_filter 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_email_filter. 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_email_filter is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.