SSH MCP Server

read-command

Read-only

Run approved read-only shell commands over SSH to inspect remote files and system state without modifying anything.

Instructions

Execute a READ-ONLY command from an allowlist (ls, cat, grep, find, stat, df, etc.). This tool does NOT modify the system. Prefer this tool for all read operations. Single-line only: a command containing a line break is refused, so upload a multi-line script with sftp-upload and run it by path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "read-command"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	Read-only shell command (must be in the allowlist)
`profile`	No	Profile name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.5.0Aug 30, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavioral constraints beyond the readOnlyHint annotation: it clarifies the tool does not modify the system, enforces a single-line-only restriction, and explains that line breaks cause refusal. It also provides a workaround, giving the agent actionable operational knowledge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, immediately stating the tool's core purpose and read-only nature. Every sentence adds value, covering scope, preference, and a key limitation with a clear alternative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete enough for this tool's complexity: it covers the allowlist, read-only behavior, single-line limitation, and how to handle multi-line scripts. Combined with the readOnlyHint annotation and fully documented parameters, an agent has sufficient information to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already documents both parameters with 100% coverage: command is described as a read-only shell command in the allowlist, and profile is described as a profile name. The description mainly reinforces the command parameter's constraints but adds little beyond the schema, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool executes a READ-ONLY command from an allowlist, naming common examples like ls, cat, grep, and find. It also distinguishes itself from siblings such as run-command and privileged-command by emphasizing the read-only, allowlisted nature.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to prefer this tool for all read operations, establishing when it should be used. It also gives a concrete alternative for multi-line scripts by directing users to upload with sftp-upload and run by path, which helps an agent avoid rejected commands.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server