pfsense_update_firewall_nat_port_forward

WHAT IT DOES

What pfsense_update_firewall_nat_port_forward does on Pfsense

AI agents use pfsense_update_firewall_nat_port_forward 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_update_firewall_nat_port_forward needs a policy

The tool name strongly suggests it updates/modifies an existing firewall NAT port forward rule on a pfSense firewall. This is a Write operation (modifying an existing rule reversibly), but with high severity since modifying NAT port forwarding rules can expose internal services to the internet or disrupt network access.

From the tool's definition Tool name: pfsense_update_firewall_nat_port_forward — 'update' indicates modification of an existing NAT port forward rule

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pfsense_update_firewall_nat_port_forward Rate-limited

pfsense_update_firewall_nat_port_forward 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_update_firewall_nat_port_forward": {
      "limits": [
        {
          "counter": "pfsense_update_firewall_nat_port_forward_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_update_firewall_nat_port_forward

What does the pfsense_update_firewall_nat_port_forward tool do? +

pfsense_update_firewall_nat_port_forward. 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_update_firewall_nat_port_forward? +

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

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

Can I rate-limit pfsense_update_firewall_nat_port_forward? +

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

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

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