Remove all MCP-created NAT fix rules
AI agents call nat_cleanup_dmz_fix to permanently remove resources in OPNSense MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes firewall NAT rules, which is an irreversible operation that cannot be undone without manual reconfiguration. Even though the scope is limited to 'MCP-created' rules, any misconfiguration or unintended execution could remove critical network routing rules, disrupting network access and communications. This meets the Destructive category definition: irreversibly deletes data/configuration.
From the tool's definition Tool name 'nat_cleanup_dmz_fix' and description 'Remove all MCP-created NAT fix rules' indicate irreversible deletion of firewall NAT rules. The word 'cleanup' combined with 'remove all' signals batch deletion without recovery mechanism.
Documented attack patterns abuse exactly the kind of access nat_cleanup_dmz_fix 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_cleanup_dmz_fix:
{
"version": "1",
"default": "deny",
"hide": [
"nat_cleanup_dmz_fix"
]
} nat_cleanup_dmz_fix disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove all MCP-created NAT fix rules. It is categorised as a Destructive tool in the OPNSense MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for nat_cleanup_dmz_fix: 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.
nat_cleanup_dmz_fix is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the nat_cleanup_dmz_fix 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 nat_cleanup_dmz_fix. 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.
nat_cleanup_dmz_fix 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.
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.