ssh_list_sessions
List all active SSH sessions and remaining connection slots.
This record as markdown: /tools/bhayanak-ssh-mcp-server/ssh-list-sessions.md
What ssh_list_sessions does on SSH MCP Server
AI agents call ssh_list_sessions to retrieve information from SSH MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why ssh_list_sessions is rated Low
This tool performs a passive enumeration of active sessions and available resources. It has no side effects, does not execute code, does not modify state, and does not delete or move money. The blast radius of misuse is minimal—an agent could only learn about what sessions exist, which is informational. Classified as Read with low severity.
From the tool's definition Tool name 'ssh_list_sessions' and description 'List all active SSH sessions and remaining connection slots' indicate a read-only query operation that retrieves status information about existing sessions without modifying or executing anything.
Attacks that exploit this kind of access
The rule that runs ssh_list_sessions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ssh_list_sessions, this is the rule to start with:
ssh_list_sessions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every ssh_list_sessions call is checked against it from then on.
Questions about ssh_list_sessions
List all active SSH sessions and remaining connection slots. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SSH MCP Server, and thousands of servers like it.
This server
Across the catalogue