pfsense_list_firewall_nat_one_to_one_mappings

A read tool on the Pfsense MCP server.

SERVERPfsense SOURCEabl030/pfsense-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/abl030-pfsense-mcp/pfsense-list-firewall-nat-one-to-one-mappings.md

WHAT IT DOES

What pfsense_list_firewall_nat_one_to_one_mappings does on Pfsense

AI agents call pfsense_list_firewall_nat_one_to_one_mappings to retrieve information from Pfsense without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why pfsense_list_firewall_nat_one_to_one_mappings is rated Low

The 'list' operation retrieves and queries NAT mappings from a pfSense firewall configuration. This is fundamentally a read operation with no side effects or reversible changes.

From the tool's definition Tool name 'pfsense_list_firewall_nat_one_to_one_mappings' uses the 'list' verb, indicating data retrieval without modification. The description is empty, but the naming pattern is consistent with read-only operations across the sibling tool set.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

pfsense_list_firewall_nat_one_to_one_mappings Allowed

pfsense_list_firewall_nat_one_to_one_mappings is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pfsense_list_firewall_nat_one_to_one_mappings": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pfsense, apply this rule, and every pfsense_list_firewall_nat_one_to_one_mappings call is checked against it from then on.

FAQ

Questions about pfsense_list_firewall_nat_one_to_one_mappings

What does the pfsense_list_firewall_nat_one_to_one_mappings tool do? +

pfsense_list_firewall_nat_one_to_one_mappings is a read tool on the Pfsense MCP server. It is categorised as a Read tool in the Pfsense MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pfsense_list_firewall_nat_one_to_one_mappings? +

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

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

Can I rate-limit pfsense_list_firewall_nat_one_to_one_mappings? +

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

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

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

KEEP EXPLORING

More on Pfsense, and thousands of servers like it.

This server

All 680 Pfsense tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →