Get gateway status including dpinger health checks.
AI agents call opn_gateway_status 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 tool retrieves current status information about gateways and their health checks. It performs a query operation with no side effects, no data modification, and no code execution. The 'Get' verb clearly indicates a read operation. This is low severity because misuse would only expose monitoring data without affecting firewall configuration or operations.
From the tool's definition Tool name 'opn_gateway_status' and description 'Get gateway status including dpinger health checks' indicate a read-only retrieval of gateway and health check information with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access opn_gateway_status 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 opn_gateway_status:
{
"version": "1",
"default": "deny",
"tools": {
"opn_gateway_status": {}
}
} opn_gateway_status 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 gateway status including dpinger health checks. 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 opn_gateway_status: 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.
opn_gateway_status 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 opn_gateway_status 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 opn_gateway_status. 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.
opn_gateway_status is provided by the OPNsense MCP Server MCP server (lucamarien/opnsense-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OPNsense MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
81 OPNsense MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.