AI agents call ssh_tunnel_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 and displays information about existing SSH tunnels. It has no side effects, does not execute commands, does not modify data, and does not delete or create resources. It is a pure information query operation, clearly falling into the Read category. The low severity reflects minimal risk even if misused—an agent listing tunnels cannot cause damage with this tool alone.
From the tool's definition Tool name 'ssh_tunnel_list' and description 'List all active SSH tunnels' indicate a read-only query operation that retrieves tunnel state information without modification or execution.
Documented attack patterns abuse exactly the kind of access ssh_tunnel_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_tunnel_list:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_tunnel_list": {}
}
}ssh_tunnel_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 tunnels. 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_tunnel_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_tunnel_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_tunnel_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_tunnel_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_tunnel_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.