Trace the network path from OPNsense to a destination host.
AI agents invoke opn_traceroute to trigger actions in OPNsense MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Traceroute actively executes a network diagnostic operation from the firewall, sending probe packets to an external destination. This is an Execute category action as it triggers external network operations whose effects depend on the destination argument. Severity is medium since it could be used to probe network topology or expose routing information, though it has no direct write or destructive impact.
From the tool's definition Trace the network path from OPNsense to a destination host
Documented attack patterns abuse exactly the kind of access opn_traceroute 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_traceroute:
{
"version": "1",
"default": "deny",
"tools": {
"opn_traceroute": {
"limits": [
{
"counter": "opn_traceroute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}opn_traceroute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Trace the network path from OPNsense to a destination host. It is categorised as a Execute tool in the OPNsense MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OPNsense MCP Server MCP server in PolicyLayer and add a rule for opn_traceroute: 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_traceroute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the opn_traceroute 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_traceroute. 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_traceroute 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.