Critical Risk →

nat_delete_port_forward

Delete a port forward rule

How to control nat_delete_port_forward ↓

AI agents call nat_delete_port_forward to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Deleting a port forwarding rule is a destructive operation that cannot be undone without manual reconfiguration. While not as critical as deleting the firewall entirely, removing network rules can disrupt traffic flows and services that depend on those rules. The action is irreversible, placing it in the Destructive category with high severity due to potential network service disruption.

From the tool's definition Tool name is 'nat_delete_port_forward' with description 'Delete a port forward rule'. The verb 'delete' indicates irreversible removal of a firewall configuration rule.

Documented attack patterns abuse exactly the kind of access nat_delete_port_forward gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and OPNSense MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for nat_delete_port_forward:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "nat_delete_port_forward"
  ]
}

nat_delete_port_forward disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the nat_delete_port_forward tool do? +

Delete a port forward rule. It is categorised as a Destructive tool in the OPNSense MCP Server 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 nat_delete_port_forward? +

Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for nat_delete_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 OPNSense MCP Server. Nothing to install.

What risk level is nat_delete_port_forward? +

nat_delete_port_forward 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 nat_delete_port_forward? +

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

Set action: deny in the PolicyLayer policy for nat_delete_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 nat_delete_port_forward? +

nat_delete_port_forward is provided by the OPNSense MCP Server MCP server (vespo92/opnsensemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OPNSense MCP Server tool call.

Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.