Low Risk

nat_list_outbound

List all outbound NAT rules

How to control nat_list_outbound ↓

AI agents call nat_list_outbound to retrieve information from OPNSense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries and returns existing outbound NAT rules configuration. It performs a simple read operation on firewall state without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an attacker gains only visibility into current NAT rules, which does not expose the ability to alter network traffic or security posture.

From the tool's definition Tool name 'nat_list_outbound' and description 'List all outbound NAT rules' indicate data retrieval with no modification or side effects.

Documented attack patterns abuse exactly the kind of access nat_list_outbound 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_list_outbound:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "nat_list_outbound": {}
  }
}

nat_list_outbound is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  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.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the nat_list_outbound tool do? +

List all outbound NAT rules. It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on nat_list_outbound? +

Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for nat_list_outbound: 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_list_outbound? +

nat_list_outbound is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit nat_list_outbound? +

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

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

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