Connect to a remote server via SSH
AI agents invoke ssh_connect to trigger actions in SSH MCP. 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.
Initiating an SSH connection to a remote server is an external operation that opens a network session and enables subsequent privileged actions (exec, file transfers, etc.). While the connection itself doesn't delete or modify data, it is a gateway operation with high blast radius — once connected, the agent can execute arbitrary commands or transfer files. Execute is the most appropriate category.
From the tool's definition "Connect to a remote server via SSH" — establishes an active SSH session to a remote system
Documented attack patterns abuse exactly the kind of access ssh_connect gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_connect:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_connect": {
"limits": [
{
"counter": "ssh_connect_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Connect to a remote server via SSH. It is categorised as a Execute tool in the SSH MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH 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. 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 (mixelpixx/ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH MCP, 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.
6 SSH MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.