pfsense_delete_firewall_nat_outbound_mappings

pfsense_delete_firewall_nat_outbound_mappings

Server Pfsense abl030/pfsense-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What pfsense_delete_firewall_nat_outbound_mappings does on Pfsense

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

Why pfsense_delete_firewall_nat_outbound_mappings needs a policy

This tool permanently removes NAT outbound mappings from a pfSense firewall. NAT configuration is mission-critical infrastructure; deleting these mappings irreversibly breaks network address translation rules, causing connectivity failures and potential service outages. An AI agent misusing this tool could disable network routing for entire network segments.

From the tool's definition Tool name contains 'delete' and targets 'firewall_nat_outbound_mappings' — a critical network configuration. The server description confirms it provides 'full control over pfSense firewalls' with 677 tools covering essential infrastructure.

Questions about pfsense_delete_firewall_nat_outbound_mappings

What does the pfsense_delete_firewall_nat_outbound_mappings tool do? +

pfsense_delete_firewall_nat_outbound_mappings. It is categorised as a Destructive tool in the Pfsense 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 pfsense_delete_firewall_nat_outbound_mappings? +

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

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

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

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

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.