ssh_connect
Open a persistent SSH session to a host.
This record as markdown: /tools/bhayanak-ssh-mcp-server/ssh-connect.md
What ssh_connect does on SSH MCP Server
AI agents invoke ssh_connect to trigger actions in SSH 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.
Why ssh_connect is rated High
Opening a persistent SSH session gives the agent (and subsequent commands) full shell access to a remote Linux server. While the connection itself is not destructive, it is the gateway to arbitrary remote code execution, making Execute the appropriate category with high severity due to the broad blast radius of unrestricted remote access.
From the tool's definition 'Open a persistent SSH session to a host' — establishes an interactive remote shell connection
Attacks that exploit this kind of access
The rule that runs ssh_connect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh_connect, this is the rule to start with:
ssh_connect 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 SSH MCP Server, apply this rule, and every ssh_connect call is checked against it from then on.
Questions about ssh_connect
Open a persistent SSH session to a host. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_connect: 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 SSH MCP Server. Nothing to install.
ssh_connect 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_connect 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_connect. 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_connect is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SSH MCP Server, and thousands of servers like it.
Across the catalogue