Read output from an interactive shell session
AI agents call ssh_shell_read 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 output from an already-established interactive shell session. It has no side effects, does not execute commands, does not modify state, and does not delete data. While it operates in the context of remote SSH sessions, the tool itself is a passive retrieval mechanism. The actual command execution and state changes are performed by ssh_shell_send and ssh_exec on the same server.
From the tool's definition Tool name is 'ssh_shell_read' and description states it 'Read[s] output from an interactive shell session' — the verb is explicitly 'read' with no modification or execution of data.
Attacks that exploit this kind of access
Read output from an interactive shell session. 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_shell_read: 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_shell_read 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_shell_read 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_shell_read. 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_shell_read is provided by the SSH MCP Server MCP server (kpanuragh/ssh-mcp). 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 →