pfsense_firewall_virtual_ip_apply

What pfsense_firewall_virtual_ip_apply does on Pfsense

AI agents invoke pfsense_firewall_virtual_ip_apply to trigger actions in Pfsense. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why pfsense_firewall_virtual_ip_apply is rated High

The 'apply' endpoint pushes pending virtual IP changes into effect on the pfSense firewall. This is an Execute-class action: it triggers an external operation (reconfiguring the live firewall's network interfaces/virtual IPs) whose effects depend on what changes were staged. Misuse could disrupt network connectivity or expose/hide services, making severity high given the blast radius on a production firewall.

From the tool's definition POST /api/v2/firewall/virtual_ip/apply — 'apply' indicates triggering an external operation that activates/commits pending virtual IP configuration changes to the live firewall

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_firewall_virtual_ip_apply": {
      "limits": [
        {
          "counter": "pfsense_firewall_virtual_ip_apply_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about pfsense_firewall_virtual_ip_apply