This record as markdown: /tools/io-github-dave-london-go/ssh-run.md
What ssh-run does on Go
AI agents invoke ssh-run to trigger actions in Go. 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.
Why ssh-run is rated High
This tool executes arbitrary shell commands on remote machines, which is a classic Execute operation. While potentially destructive depending on the command argument, the primary capability is command execution on external systems. The high severity reflects the broad blast radius—an AI agent misusing this tool could compromise remote infrastructure, exfiltrate data, disrupt services, or pivot to other systems.
From the tool's definition Tool description states 'Executes a command on a remote host via SSH' and explicitly warns 'This runs commands on a remote machine.' The tool runs arbitrary commands on external systems with full access to their execution environment.
Attacks that exploit this kind of access
The rule that runs ssh-run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh-run, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every ssh-run call is checked against it from then on.
Questions about ssh-run
Executes a command on a remote host via SSH. WARNING: This runs commands on a remote machine. Ensure the host and command are correct before executing. Returns structured output with stdout, stderr, exit code, and duration. It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Go 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 Go. 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 Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Go, and thousands of servers like it.
This server
Across the catalogue