safe-ssh-mcp

Overview Schema Source Related Servers Discussions Admin

get_docker_images

Collect Docker image repository, tag, digest, ID, age, and size data from a remote Linux host over SSH, including passwordless sudo or doas when daemon access is restricted.

Instructions

Collects docker images --digests output (repository, tag, digest, image ID, age, size) from a remote Linux host via SSH When the login user cannot reach the docker daemon (not root, not in the docker group), the command is run through passwordless sudo or doas (sudo -n / doas -n).

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": {
      "host": "<host>",
      "user": "<user>"
    },
    "name": "get_docker_images"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes
`port`	No
`user`	Yes
`timeout`	No
`key_path`	No
`password`	No
`accept_new_hostkey`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.16Nov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose non-obvious behavior — SSH execution and automatic privilege escalation via 'sudo -n'/'doas -n' when the login user cannot reach the daemon. It does not state that the operation is read-only, what happens on escalation failure, or how timeouts behave.

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?

Two tight sentences, front-loading what is collected before the privilege-escalation caveat. No filler or repetition.

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

Completeness2/5

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

An output schema exists so return values need not be described, but for a 7-parameter SSH tool with zero schema coverage and no annotations, the description leaves the authentication and host-verification parameters unexplained — a material gap for correct invocation.

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

Parameters2/5

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

Seven parameters with 0% schema description coverage, and the description explains none of them. Only 'host' and 'user' are loosely implied by 'remote Linux host' and 'login user'; authentication choice (key_path vs password vs agent), port, timeout, and accept_new_hostkey semantics are entirely undocumented.

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?

Names the exact command and resource ('docker images --digests') and enumerates the returned fields (repository, tag, digest, image ID, age, size), making it straightforwardly distinguishable from siblings like get_docker_ps_all or get_docker_inspect.

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

Usage Guidelines3/5

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

Usage is implied by the command name and the remote-host framing, but there is no explicit when-to-use/when-not-to-use guidance versus get_crictl_images or get_docker_inspect. The sudo/doas fallback condition is the only situational guidance offered.

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

Deploy Server