// SCAN REPORT

SSH MCP Server

15 tools. 11 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 12 Jun 2026

11 can modify or destroy data

4 read-only

15 tools total

Community server · catalogue entry verified 12/06/2026

How to control SSH MCP Server ↓

TOOL MAP

What SSH MCP Server exposes to your agents

Read (4) Write / Execute (10) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous SSH MCP Server tools

Destructive · High remove_credential This tool permanently deletes a stored SSH credential. Execute · High ssh_exec This tool triggers external operations (remote command execution) whose effects are entirely dependent on the command argument provided. Execute · High ssh_exec_raw This tool executes commands on remote systems via SSH. Execute · Medium ssh_session_end Ending an SSH session is a consequential action that triggers external operations on a remote system—the session termination itself and any cleanup or signal handling it performs.

11 of SSH MCP Server's 15 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control SSH MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "remove_credential": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_credential": {
    "limits": [
      {
        "counter": "add_credential_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_credentials": {
    "limits": [
      {
        "counter": "list_credentials_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register SSH MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SSH →

Free to start. No card required.

FULL CATALOGUE

All 15 SSH MCP Server tools

DESTRUCTIVE 1 tools

Destructive remove_credential Remove a stored SSH credential

EXECUTE 8 tools

Execute ssh_exec Execute command over SSH using stored credentials Execute ssh_exec_raw Execute command over SSH with array arguments that are safely quoted for the remote shell Execute ssh_session_end End an interactive SSH session Execute ssh_session_start Start an interactive SSH session with PTY (for vim, htop, etc) Execute ssh_tunnel_start Start an SSH tunnel for port forwarding Execute ssh_tunnel_stop Stop an SSH tunnel Execute rsync_copy Copy files/directories between local and remote server via rsync (best for directories or large transfers) Execute ssh_session_send Send input to an interactive SSH session

WRITE 2 tools

Write add_credential Add a new SSH credential with private key file path Write scp_copy Copy a single file between local and remote server via SFTP (simpler than rsync for single files)

READ 4 tools

Read list_credentials List all stored SSH credentials Read ssh_session_list List all active SSH sessions Read ssh_session_read Read output from an interactive SSH session Read ssh_tunnel_list List all active SSH tunnels

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about SSH MCP Server

Can an AI agent delete data through the SSH MCP Server MCP server? +

Yes. The SSH MCP Server server exposes 1 destructive tools including remove_credential. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through SSH MCP Server? +

The SSH MCP Server server has 2 write tools including add_credential, scp_copy. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach SSH MCP Server.

How many tools does the SSH MCP Server MCP server expose? +

15 tools across 4 categories: Destructive, Execute, Read, Write. 4 are read-only. 11 can modify, create, or delete data.

How do I enforce a policy on SSH MCP Server? +

Register the SSH MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every SSH MCP Server tool call.

Deterministic rules across all 15 SSH MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SSH →

Free to start. No card required.

15 SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.