AI agents call pfsense_get_firewall_nat_outbound_mapping to retrieve information from Pfsense without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves (queries) firewall NAT configuration data with no side effects or reversible/irreversible modifications. While the severity is elevated from 'low' to 'medium' because NAT mappings are security-sensitive network infrastructure details that could inform attackers about network topology and traffic routing, the action itself is read-only with no capability to alter system state.
From the tool's definition Tool name contains 'get' and description shows 'GET /api/v2/firewall/nat/outbound/mapping' — a read-only HTTP GET request that retrieves firewall NAT outbound mapping configuration data without modification.
Attacks that exploit this kind of access
GET /api/v2/firewall/nat/outbound/mapping. It is categorised as a Read tool in the Pfsense MCP Server, which means it retrieves data without modifying state.
Register the Pfsense MCP server in PolicyLayer and add a rule for pfsense_get_firewall_nat_outbound_mapping: 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.
pfsense_get_firewall_nat_outbound_mapping is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pfsense_get_firewall_nat_outbound_mapping 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.
Set action: deny in the PolicyLayer policy for pfsense_get_firewall_nat_outbound_mapping. 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.
pfsense_get_firewall_nat_outbound_mapping 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →