ssh_connect_with_credential · MCP SSH Server MCP

WHAT IT DOES

What ssh_connect_with_credential does on MCP SSH Server

AI agents invoke ssh_connect_with_credential to trigger actions in MCP SSH 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 IT NEEDS A POLICY

Why ssh_connect_with_credential needs a policy

Establishing an SSH connection initiates an active session to a remote server, which is an external operation with significant side effects. Once connected, subsequent commands can be executed on the remote system. This goes beyond a simple read/write operation — it triggers an external network operation and opens a persistent channel that can be leveraged for arbitrary remote execution.

From the tool's definition Connect to SSH server using saved credentials

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_connect_with_credential Rate-limited

ssh_connect_with_credential 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_connect_with_credential": {
      "limits": [
        {
          "counter": "ssh_connect_with_credential_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP SSH Server, so you can run agents against it safely.

FAQ

Questions about ssh_connect_with_credential

What does the ssh_connect_with_credential tool do? +

Connect to SSH server using saved credentials. It is categorised as a Execute tool in the MCP SSH Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssh_connect_with_credential? +

Register the MCP SSH Server MCP server in PolicyLayer and add a rule for ssh_connect_with_credential: 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 Server. Nothing to install.

What risk level is ssh_connect_with_credential? +

ssh_connect_with_credential is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssh_connect_with_credential? +

Yes. Add a rate_limit block to the ssh_connect_with_credential 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.

How do I block ssh_connect_with_credential completely? +

Set action: deny in the PolicyLayer policy for ssh_connect_with_credential. 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.

What MCP server provides ssh_connect_with_credential? +

ssh_connect_with_credential is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.