Execute multiple commands in sequence via SSH
AI agents invoke ssh_batch_execute 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 shell commands on OPNSense firewall systems with no specified restrictions on command scope. Batch execution of SSH commands can alter firewall configuration, network routing, security policies, or system state depending on the commands passed. The blast radius is critical—an AI agent could reconfigure firewalls, disable security controls, modify access rules, or compromise network infrastructure.
From the tool's definition Tool name 'ssh_batch_execute' and description 'Execute multiple commands in sequence via SSH' directly indicate execution of arbitrary commands on remote systems via SSH protocol.
Documented attack patterns abuse exactly the kind of access ssh_batch_execute 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_batch_execute:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_batch_execute": {
"limits": [
{
"counter": "ssh_batch_execute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ssh_batch_execute 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.
Execute multiple commands in sequence 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_batch_execute: 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_batch_execute 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_batch_execute 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_batch_execute. 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_batch_execute 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.