Execute SSH command with policy, network checks, progress, timeout, and cancellation.
AI agents invoke ssh_run to trigger actions in MCP SSH Orchestrator. 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 arbitrary SSH commands on remote server fleets. While the server implements policy controls and audit logging, the tool's core function is Execute—triggering external operations (remote commands) whose effects depend entirely on the arguments provided. An AI agent could misuse this to run destructive or unauthorized commands across infrastructure, making it Execute rather than Read or Write.
From the tool's definition Tool name 'ssh_run' with description stating 'Execute SSH command' directly indicates command execution capability.
Documented attack patterns abuse exactly the kind of access ssh_run gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SSH Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_run:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_run": {
"limits": [
{
"counter": "ssh_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ssh_run 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 SSH command with policy, network checks, progress, timeout, and cancellation. It is categorised as a Execute tool in the MCP SSH Orchestrator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP SSH Orchestrator MCP server in PolicyLayer and add a rule for ssh_run: 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 MCP SSH Orchestrator. Nothing to install.
ssh_run 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_run 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_run. 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_run is provided by the MCP SSH Orchestrator MCP server (samerfarida/mcp-ssh-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP SSH Orchestrator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MCP SSH Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.