safe-ssh-mcp

Overview Schema Source Related Servers Discussions Admin

get_mounts

List mounted filesystems with mount points, source devices, types, and options to spot read-only remounts after errors and check flags such as noexec, nosuid, or network and tmpfs mounts.

Instructions

Lists mounted filesystems with their mount point, source device, filesystem type and mount options (findmnt, as a tree; /proc/mounts if findmnt is not installed). USE THIS TOOL to find a filesystem that was remounted read-only after an error ('ro' in the options), to check options like noexec/nosuid, and to see network (nfs, cifs), overlay and tmpfs mounts. For free space use get_disk_free instead.

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_mounts"
  }
}

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.2.0Nov 13, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does disclose implementation details beyond the schema: the command used, the tree layout, and the /proc/mounts fallback when findmnt is absent. However, it never states that this connects over SSH using the supplied host/user credentials, nor whether elevated privileges are needed to see all mounts, leaving real behavioral gaps for a host-inspection tool.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence with the data-source caveat parenthesized rather than sprawling, and the second sentence is dedicated to usage. Every clause earns its place; only the slightly dense run-on structure of the usage sentence costs a point.

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

Completeness3/5

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

Return values need not be explained because an output schema exists, and the description covers purpose, source and routing well. For a seven-parameter remote-host tool with no annotations, though, the absence of any authentication or permission guidance leaves the definition short of complete.

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?

Schema description coverage is 0% across seven parameters, so the description must compensate for host, port, user, timeout, key_path, password and accept_new_hostkey. It says nothing about any of them, not even that host and user are required SSH connection details or that authentication is via key_path or password. The only hint is the implicit mention of findmnt, which implies a remote shell but explains no parameter.

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 opens with a specific verb and resource ('Lists mounted filesystems') and enumerates exactly what each entry contains: mount point, source device, filesystem type and mount options. It also names its data source (findmnt, falling back to /proc/mounts) and explicitly separates itself from the disk-space sibling, so an agent can distinguish it without opening the schema.

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 gives concrete when-to-use conditions: spotting a filesystem remounted read-only ('ro' in options) after an error, checking noexec/nosuid, and inspecting nfs/cifs, overlay and tmpfs mounts. It also provides an explicit exclusion and redirect ('For free space use get_disk_free instead'), which is exactly the routing information an agent needs.

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

Deploy Server