AI agents use pfsense_create_services_haproxy_backend to create or update resources in Pfsense — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pfsense environment.
The 'create' verb indicates this tool modifies system configuration by adding a new HAProxy backend service. HAProxy backend configuration controls traffic routing and load balancing on the firewall. While reversible (Write category), misconfiguration could disrupt network traffic flows, affecting service availability.
From the tool's definition Tool name indicates 'create' operation on HAProxy backend services in pfSense. Description is empty, but the server description states it gives 'full control over pfSense firewalls' including 'services', and the naming pattern matches sibling tools that are…
Attacks that exploit this kind of access
pfsense_create_services_haproxy_backend. It is categorised as a Write tool in the Pfsense MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_services_haproxy_backend: 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_create_services_haproxy_backend is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the pfsense_create_services_haproxy_backend 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_create_services_haproxy_backend. 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_create_services_haproxy_backend 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.
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 →