AI agents call ssh_list_config 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 and enumerates SSH connection configurations from a config file. While it is a Read operation (no side effects), the severity is medium rather than low because SSH configuration data can contain sensitive information such as hostnames, usernames, ports, and key paths that could be used to map network infrastructure or identify attack targets.
From the tool's definition Tool description translates to 'List all SSH connections in the configuration file'. The verb 'list' indicates data retrieval without modification. The tool reads SSH configuration entries.
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_config: 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_config 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_config 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_config. 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_config 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 →