High Risk →

routing_fix_all

Automatically fix all detected inter-VLAN routing issues

How to control routing_fix_all ↓

AI agents invoke routing_fix_all 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.

High Risk

This tool automatically modifies firewall/routing configuration to fix inter-VLAN routing issues. It triggers operational changes to network routing rules and firewall settings, which is an Execute-level action. The blast radius is high because misconfigured routing changes on a firewall could disrupt network connectivity across VLANs or expose network segments.

From the tool's definition "Automatically fix all detected inter-VLAN routing issues"

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access routing_fix_all 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 routing_fix_all:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "routing_fix_all": {
      "limits": [
        {
          "counter": "routing_fix_all_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register OPNSense MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the routing_fix_all tool do? +

Automatically fix all detected inter-VLAN routing issues. 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_fix_all? +

Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for routing_fix_all: 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_fix_all? +

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

Can I rate-limit routing_fix_all? +

Yes. Add a rate_limit block to the routing_fix_all 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_fix_all completely? +

Set action: deny in the PolicyLayer policy for routing_fix_all. 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_fix_all? +

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.