Get current NAT mode (automatic, hybrid, manual, disabled)
AI agents call nat_get_mode to retrieve information from OPNSense MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only query operation that retrieves the current NAT mode setting from the OPNSense firewall. It does not create, modify, delete, or execute any actions—it only fetches and returns existing configuration state. The blast radius of misuse is minimal as an AI agent cannot cause harm by querying this setting.
From the tool's definition Tool name and description indicate it 'Get[s] current NAT mode' with no parameters for modification. Returns status of existing configuration without side effects.
Documented attack patterns abuse exactly the kind of access nat_get_mode 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_get_mode:
{
"version": "1",
"default": "deny",
"tools": {
"nat_get_mode": {}
}
}nat_get_mode is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get current NAT mode (automatic, hybrid, manual, disabled). It is categorised as a Read tool in the OPNSense MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for nat_get_mode: 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_get_mode 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 nat_get_mode 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_get_mode. 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_get_mode 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.