routing_diagnostics

THE RISK

High Risk

This tool executes diagnostic commands that probe and analyze routing behavior between VLANs. While diagnostics are typically non-destructive and read-oriented, the 'Run' verb and the comprehensive nature of inter-VLAN routing diagnostics suggest active execution of diagnostic routines (such as traceroute, ping, or routing table queries) that could have side effects on network state or reveal sensitive routing…

From the tool's definition Tool performs 'comprehensive inter-VLAN routing diagnostics' which involves running diagnostic operations that execute queries/commands against network routing infrastructure.

Documented attack patterns abuse exactly the kind of access routing_diagnostics gives an agent:

HOW TO CONTROL ROUTING_DIAGNOSTICS

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 routing_diagnostics:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "routing_diagnostics": {
      "limits": [
        {
          "counter": "routing_diagnostics_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

routing_diagnostics 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.

Create a free account and register OPNSense MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More OPNSense MCP Server tools

Destructive acme_delete_action Delete an ACME automation action Destructive acme_revoke_certificate Revoke a certificate Destructive cert_delete Delete a certificate Destructive delete_firewall_rule Delete a firewall rule Destructive delete_vlan Delete a VLAN Destructive firewall_delete_rule Delete a firewall rule Destructive haproxy_acl_delete Delete an HAProxy ACL Destructive haproxy_action_delete Delete an HAProxy action

All 196 OPNSense MCP Server tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in OPNSense MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the routing_diagnostics tool do? +

Run comprehensive inter-VLAN routing diagnostics. 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.

How do I enforce a policy on routing_diagnostics? +

Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for routing_diagnostics: 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.

What risk level is routing_diagnostics? +

routing_diagnostics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit routing_diagnostics? +

Yes. Add a rate_limit block to the routing_diagnostics 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.

How do I block routing_diagnostics completely? +

Set action: deny in the PolicyLayer policy for routing_diagnostics. 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.

What MCP server provides routing_diagnostics? +

routing_diagnostics 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.

Enforce policy on every OPNSense MCP Server tool call.

Deterministic rules across all 196 OPNSense MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN OPNSENSE →

Free to start. No card required.

196 OPNSense MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT ROUTING_DIAGNOSTICS ON OPNSENSE MCP SERVER DOES

// THE RISK

// HOW TO CONTROL ROUTING_DIAGNOSTICS

// EXPLORE