pfsense_delete_services_haproxy_backend_acl

A destructive tool on the Pfsense MCP server.

SERVERPfsense SOURCEabl030/pfsense-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-delete-services-haproxy-backend-acl.md

WHAT IT DOES

What pfsense_delete_services_haproxy_backend_acl does on Pfsense

AI agents call pfsense_delete_services_haproxy_backend_acl 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.

RISK

Why pfsense_delete_services_haproxy_backend_acl is rated Critical

The 'delete' verb in 'pfsense_delete_services_haproxy_backend_acl' combined with the context of a pfSense firewall management server indicates this tool permanently removes HAProxy backend ACL configurations. This is a destructive action that cannot be undone without manual restoration or backups.

From the tool's definition Tool name contains 'delete' action on pfSense HAProxy backend ACL configuration. Server description indicates 'full control over pfSense firewalls' with 677 tools managing firewall rules, services, and configurations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pfsense_delete_services_haproxy_backend_acl 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_backend_acl, this is the rule to start with:

pfsense_delete_services_haproxy_backend_acl Hidden

pfsense_delete_services_haproxy_backend_acl is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "pfsense_delete_services_haproxy_backend_acl"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_delete_services_haproxy_backend_acl call is checked against it from then on.

FAQ

Questions about pfsense_delete_services_haproxy_backend_acl

What does the pfsense_delete_services_haproxy_backend_acl tool do? +

pfsense_delete_services_haproxy_backend_acl is a destructive tool on the Pfsense MCP server. 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.

How do I enforce a policy on pfsense_delete_services_haproxy_backend_acl? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_delete_services_haproxy_backend_acl: 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.

What risk level is pfsense_delete_services_haproxy_backend_acl? +

pfsense_delete_services_haproxy_backend_acl is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pfsense_delete_services_haproxy_backend_acl? +

Yes. Add a rate_limit block to the pfsense_delete_services_haproxy_backend_acl 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.

How do I block pfsense_delete_services_haproxy_backend_acl completely? +

Set action: deny in the PolicyLayer policy for pfsense_delete_services_haproxy_backend_acl. 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.

What MCP server provides pfsense_delete_services_haproxy_backend_acl? +

pfsense_delete_services_haproxy_backend_acl 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.

KEEP EXPLORING

More on Pfsense, and thousands of servers like it.

This server

All 680 Pfsense tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →