AI agents call ssh_list_connections to retrieve information from Ssh Agent without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or enumerates SSH connection metadata. It performs no side effects, does not execute commands, does not modify data, and does not delete resources. It falls squarely into the Read category. Severity is low because listing connections has minimal blast radius—the worst case is information disclosure about which connections exist, which does not directly impact system security or data integrity.
From the tool's definition Tool name 'ssh_list_connections' and description '列出所有SSH连接' (list all SSH connections) indicate a retrieval operation that queries existing SSH connections without modifying or executing any operations.
Attacks that exploit this kind of access
列出所有SSH连接. It is categorised as a Read tool in the Ssh Agent MCP Server, which means it retrieves data without modifying state.
Register the Ssh Agent MCP server in PolicyLayer and add a rule for ssh_list_connections: 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 Agent. Nothing to install.
ssh_list_connections 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_connections 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_connections. 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_connections is provided by the Ssh Agent MCP server (zhijun/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 →