AI agents invoke ssh_spawn to trigger actions in Mcpx. 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.
Despite the empty description, the tool name 'ssh_spawn' strongly implies spawning an SSH session or process. In context of a shell/SSH mastery server with sibling tools like shell_exec and shell_spawn, this tool almost certainly initiates an interactive SSH session, enabling arbitrary remote command execution on external systems.
From the tool's definition Tool name 'ssh_spawn' on a server described as enabling 'command execution, interactive sessions, file transfer, and port forwarding with auditing and policy controls'; sibling tools include shell_exec, shell_script, shell_spawn — all execution-oriented.
Attacks that exploit this kind of access
ssh_spawn. It is categorised as a Execute tool in the Mcpx MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcpx MCP server in PolicyLayer and add a rule for ssh_spawn: 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 Mcpx. Nothing to install.
ssh_spawn 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_spawn 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_spawn. 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_spawn is provided by the Mcpx MCP server (rmednitzer/relay-shell). 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 →