Upload a script file and execute it on the remote server
AI agents invoke ssh_upload_and_execute to trigger actions in SSH MCP Server. 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 both uploads arbitrary content and immediately executes it on a remote server. The combination of file upload plus remote code execution represents maximum blast radius — an attacker or misconfigured agent could run any malicious script on a remote system.
From the tool's definition 'Upload a script file and execute it on the remote server'
Attacks that exploit this kind of access
Upload a script file and execute it on the remote server. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for ssh_upload_and_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 MCP Server. Nothing to install.
ssh_upload_and_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_upload_and_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_upload_and_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_upload_and_execute is provided by the SSH MCP Server MCP server (zibdie/ssh-mcp-server). 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 →