pfsense_delete_services_haproxy_backend_acl

pfsense_delete_services_haproxy_backend_acl

Server Pfsense abl030/pfsense-mcp
Category Destructive
Risk class Critical
Parameters 00 required

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.

Why pfsense_delete_services_haproxy_backend_acl needs a policy

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.

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

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.