AI agents call opn_list_static_routes 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.
The 'list' prefix strongly suggests this tool retrieves and displays static route configurations from the OPNsense firewall without modifying them. Listing routes is a read-only diagnostic operation. While the description is empty (reducing confidence slightly), the naming convention is unambiguous: 'list' operations are inherently Read category.
From the tool's definition Tool name 'opn_list_static_routes' contains 'list', which is a retrieval operation with no side effects. The verb 'list' explicitly indicates querying or enumerating data rather than modifying, deleting, or executing operations.
Documented attack patterns abuse exactly the kind of access opn_list_static_routes 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_list_static_routes:
{
"version": "1",
"default": "deny",
"tools": {
"opn_list_static_routes": {}
}
}opn_list_static_routes 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.
opn_list_static_routes. 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_list_static_routes: 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_list_static_routes 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_list_static_routes 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_list_static_routes. 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_list_static_routes 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.