pfsense_delete_services_haproxy_settings_email_mailer
DELETE /api/v2/services/haproxy/settings/email_mailer
This record as markdown: /tools/abl030-pfsense-mcp/pfsense-delete-services-haproxy-settings-email-mailer.md
What pfsense_delete_services_haproxy_settings_email_mailer does on Pfsense
AI agents call pfsense_delete_services_haproxy_settings_email_mailer to permanently remove resources in Pfsense, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why pfsense_delete_services_haproxy_settings_email_mailer is rated Critical
The tool performs an irreversible deletion of firewall service configuration (HAProxy email mailer settings). This is destructive because: (1) it uses the DELETE HTTP method indicating removal, (2) deleted configuration settings cannot be recovered without manual reconfiguration, (3) misuse could disable critical notification/alerting infrastructure on the firewall.
From the tool's definition Tool name contains 'delete' and description shows 'DELETE /api/v2/services/haproxy/settings/email_mailer' - this irreversibly removes HAProxy email mailer configuration settings.
Attacks that exploit this kind of access
The rule that runs pfsense_delete_services_haproxy_settings_email_mailer safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Pfsense, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pfsense_delete_services_haproxy_settings_email_mailer, this is the rule to start with:
pfsense_delete_services_haproxy_settings_email_mailer 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 Pfsense, apply this rule, and every pfsense_delete_services_haproxy_settings_email_mailer call is checked against it from then on.
Questions about pfsense_delete_services_haproxy_settings_email_mailer
DELETE /api/v2/services/haproxy/settings/email_mailer. It is categorised as a Destructive tool in the Pfsense MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_services_haproxy_settings_email_mailer: 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 Pfsense. Nothing to install.
pfsense_delete_services_haproxy_settings_email_mailer 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 pfsense_delete_services_haproxy_settings_email_mailer 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 pfsense_delete_services_haproxy_settings_email_mailer. 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.
pfsense_delete_services_haproxy_settings_email_mailer is provided by the Pfsense MCP server (abl030/pfsense-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Pfsense, and thousands of servers like it.
Across the catalogue