AI agents call ssh_session_list 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 active SSH sessions without making changes, executing code, or triggering side effects. Listing sessions is a read-only information retrieval operation. The severity is low because the information disclosed is limited to session metadata that an authenticated user would typically already have visibility into, and there is no capability to modify, delete, or execute operations.
From the tool's definition Tool name 'ssh_session_list' and description 'List all active SSH sessions' indicate a query/enumeration operation with no modifications or execution of commands.
Documented attack patterns abuse exactly the kind of access ssh_session_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_session_list:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_session_list": {}
}
} ssh_session_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active SSH sessions. 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_session_list: 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_session_list 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_session_list 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_session_list. 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_session_list is provided by the SSH MCP Server MCP server (kinothe-kafkaesque/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
15 SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.