AI agents use upload_file to create or update resources in Mcp Ssh — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ssh environment.
Upload_file creates or modifies files on a remote system, making it a Write operation. Severity is high because uploading malicious files could enable code execution, privilege escalation, or system compromise. Confidence is 0.85 rather than higher because the tool description is empty, limiting certainty, but the name and server context strongly indicate file write operations.
From the tool's definition Tool named 'upload_file' on SSH server context that 'enabling command execution, system monitoring, file operations' suggests file transfer capability to remote server. Server description indicates SSH-based file operations.
Attacks that exploit this kind of access
upload_file. It is categorised as a Write tool in the Mcp Ssh MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ssh MCP server in PolicyLayer and add a rule for 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 Mcp Ssh. Nothing to install.
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 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 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.
upload_file is provided by the Mcp Ssh MCP server (zhouxiangjing/mcp-ssh). 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 →