pfsense_delete_firewall_nat_one_to_one_mappings

WHAT IT DOES

What pfsense_delete_firewall_nat_one_to_one_mappings does on Pfsense

AI agents call pfsense_delete_firewall_nat_one_to_one_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 IT NEEDS A POLICY

Why pfsense_delete_firewall_nat_one_to_one_mappings needs a policy

This tool deletes NAT configuration entries, which cannot be undone and directly impacts network operations. Deletion of firewall configurations is a destructive action with potential for severe business disruption.

From the tool's definition Tool name contains 'delete' and operates on firewall NAT one-to-one mappings, which are network configuration rules.

Attacks that exploit this kind of access

Questions about pfsense_delete_firewall_nat_one_to_one_mappings

What does the pfsense_delete_firewall_nat_one_to_one_mappings tool do? +

pfsense_delete_firewall_nat_one_to_one_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_one_to_one_mappings? +

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

pfsense_delete_firewall_nat_one_to_one_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_one_to_one_mappings? +

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

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

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