AI agents invoke ssh_start_interactive 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 enables execution of arbitrary shell commands and scripts on remote systems via SSH, including privileged operations (sudo). While not irreversibly destructive by itself, it can be used to run any command including destructive operations. The interactive nature and explicit mention of sudo elevation makes this an Execute risk rather than Write or Read.
From the tool's definition Tool description indicates it 'starts interactive SSH session' and explicitly supports 'sudo, vim, mysql and other commands requiring interactive input'.
Attacks that exploit this kind of access
启动交互式SSH会话(支持sudo、vim、mysql等需要交互输入的命令). 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_start_interactive: 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_start_interactive 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_start_interactive 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_start_interactive. 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_start_interactive 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 →