Get file information (size, permissions, etc.)
AI agents call ssh_file_info to retrieve information from MCP SSH Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries file attributes (size, permissions) on a remote system via SSH. It performs no write operations, does not execute code, and does not delete or transfer data. It is a read-only query operation with minimal blast radius—the worst outcome is information disclosure about file system structure and permissions on the remote server.
From the tool's definition Tool name 'ssh_file_info' and description 'Get file information (size, permissions, etc.)' indicates retrieval of file metadata without modification or execution. No side effects beyond querying file system state.
Attacks that exploit this kind of access
Get file information (size, permissions, etc.). It is categorised as a Read tool in the MCP SSH Server MCP Server, which means it retrieves data without modifying state.
Register the MCP SSH Server MCP server in PolicyLayer and add a rule for ssh_file_info: 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 MCP SSH Server. Nothing to install.
ssh_file_info 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_file_info 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_file_info. 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_file_info is provided by the MCP SSH Server MCP server (mahathirmuh/mcp-ssh-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 →