Enable inter-VLAN routing on a specific interface
AI agents use interface_enable_intervlan_routing to create or update resources in OPNSense MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OPNSense MCP Server environment.
This tool modifies network interface configuration by enabling inter-VLAN routing. While this is a configuration change rather than deletion, it is a Write action that alters firewall behavior and can have substantial blast radius if applied incorrectly to production networks, potentially opening unintended network paths. It is reversible (can be disabled), distinguishing it from Destructive.
From the tool's definition Tool enables a network configuration change ('Enable inter-VLAN routing on a specific interface'), which modifies firewall interface settings. This is a reversible but significant network configuration alteration.
Documented attack patterns abuse exactly the kind of access interface_enable_intervlan_routing 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 interface_enable_intervlan_routing:
{
"version": "1",
"default": "deny",
"tools": {
"interface_enable_intervlan_routing": {
"limits": [
{
"counter": "interface_enable_intervlan_routing_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}interface_enable_intervlan_routing stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Enable inter-VLAN routing on a specific interface. It is categorised as a Write tool in the OPNSense MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the OPNSense MCP Server MCP server in PolicyLayer and add a rule for interface_enable_intervlan_routing: 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.
interface_enable_intervlan_routing is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the interface_enable_intervlan_routing 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 interface_enable_intervlan_routing. 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.
interface_enable_intervlan_routing 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.
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.