AI agents invoke ssh_execute to trigger actions in Ssh Agent. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary commands on remote SSH connections. Command execution is inherently an Execute category risk—effects are unpredictable and depend entirely on what commands an AI agent chooses to run. While not immediately destructive, the blast radius is high because SSH execution can modify system state, read sensitive files, or pivot to other systems.
From the tool's definition Tool name 'ssh_execute' and description '在SSH连接上执行命令' (execute commands over SSH connection) directly indicate command execution capability on remote systems.
Attacks that exploit this kind of access
在SSH连接上执行命令. It is categorised as a Execute tool in the Ssh Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ssh Agent MCP server in PolicyLayer and add a rule for ssh_execute: 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_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ssh_execute 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_execute. 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_execute 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 →