AI agents use ssh_upload_file to create or update resources in Ssh Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ssh Agent environment.
This tool creates or modifies data on remote systems by uploading files—a reversible write operation. It is not destructive (does not delete), not financial, and not execute/code-running in itself, though it could be used to stage malicious payloads.
From the tool's definition ssh_upload_file transfers files to remote servers (description: '上传文件到远程服务器' = 'upload file to remote server'); sibling tools include ssh_execute and ssh_download_file, indicating this server manages remote command execution and file transfer capabilities.
Attacks that exploit this kind of access
上传文件到远程服务器. It is categorised as a Write tool in the Ssh Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ssh Agent MCP server in PolicyLayer and add a rule for ssh_upload_file: 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_upload_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ssh_upload_file 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_file. 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_file 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 →