Apply comprehensive DMZ routing fix via SSH
AI agents invoke ssh_fix_dmz_routing 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.
This tool executes SSH commands to modify DMZ routing on a firewall. SSH execution of network configuration changes on a security device (OPNSense firewall) carries critical blast radius - misconfiguration could expose internal networks, break segmentation, or disrupt all traffic. The 'apply' and 'fix' nature implies active execution of commands, not just reading state.
From the tool's definition 'Apply comprehensive DMZ routing fix via SSH' - executes commands over SSH to modify firewall/network routing configuration
Documented attack patterns abuse exactly the kind of access ssh_fix_dmz_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 ssh_fix_dmz_routing:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_fix_dmz_routing": {
"limits": [
{
"counter": "ssh_fix_dmz_routing_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} ssh_fix_dmz_routing 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.
Apply comprehensive DMZ routing fix via SSH. 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 ssh_fix_dmz_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.
ssh_fix_dmz_routing 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 ssh_fix_dmz_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 ssh_fix_dmz_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.
ssh_fix_dmz_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.