pfsense_create_services_haproxy_backend_action

WHAT IT DOES

What pfsense_create_services_haproxy_backend_action does on Pfsense

AI agents use pfsense_create_services_haproxy_backend_action 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.

WHY IT NEEDS A POLICY

Why pfsense_create_services_haproxy_backend_action needs a policy

The tool name implies creating an HAProxy backend action configuration in pfSense's HAProxy service. This is a Write operation as it creates a new configuration entry. However, the description is empty, lowering confidence. Given the context of a pfSense firewall management server and the pattern of sibling tools (all 'create_*'), this is almost certainly a Write operation.

From the tool's definition Tool name contains 'create' suggesting creation of a new resource; 'haproxy_backend_action' suggests configuring HAProxy load balancer backend actions on a pfSense firewall

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_create_services_haproxy_backend_action Rate-limited

pfsense_create_services_haproxy_backend_action stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_create_services_haproxy_backend_action": {
      "limits": [
        {
          "counter": "pfsense_create_services_haproxy_backend_action_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Pfsense, so you can run agents against it safely.

FAQ

Questions about pfsense_create_services_haproxy_backend_action

What does the pfsense_create_services_haproxy_backend_action tool do? +

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

How do I enforce a policy on pfsense_create_services_haproxy_backend_action? +

Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_create_services_haproxy_backend_action: 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_create_services_haproxy_backend_action? +

pfsense_create_services_haproxy_backend_action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pfsense_create_services_haproxy_backend_action? +

Yes. Add a rate_limit block to the pfsense_create_services_haproxy_backend_action 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_create_services_haproxy_backend_action completely? +

Set action: deny in the PolicyLayer policy for pfsense_create_services_haproxy_backend_action. 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_create_services_haproxy_backend_action? +

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