List files and directories on the remote server
AI agents call ssh_list_files to retrieve information from SSH MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about files and directories on a remote system without creating, modifying, deleting, or executing anything. It is a non-destructive read operation similar to 'ls' or 'find' commands used for discovery and inspection. The severity is low because misuse would only expose directory structure information, not enable unauthorized actions or data modification.
From the tool's definition Tool name 'ssh_list_files' and description 'List files and directories on the remote server' indicate a query/retrieval operation with no modification or execution of code.
Attacks that exploit this kind of access
List files and directories on the remote server. It is categorised as a Read tool in the SSH MCP Server MCP Server, which means it retrieves data without modifying state.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_list_files: 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 SSH MCP Server. Nothing to install.
ssh_list_files is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssh_list_files 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.
Set action: deny in the PolicyLayer policy for ssh_list_files. 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.
ssh_list_files is provided by the SSH MCP Server MCP server (zibdie/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →