Upload a single file from the local machine to a remote SSH server. This tool establishes an SSH connection and transfers a local file to the specified remote path using SFTP protocol for reliable file transfer. Args: - host (string): SSH server hostname or IP address - port (number): SSH server ...
AI agents use ssh_upload_file to create or update resources in SSH MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH MCP Server environment.
The tool creates or modifies files on remote servers, which is reversible (files can be deleted or overwritten later). This places it in the Write category rather than Destructive. Severity is high because an AI agent could upload malicious scripts, configurations, or data to production servers, potentially compromising system integrity or enabling further attacks.
From the tool's definition Tool description states it 'transfers a local file to the specified remote path' and 'Upload a single file from the local machine to a remote SSH server.' This is a file creation/modification operation on remote infrastructure.
Attacks that exploit this kind of access
Upload a single file from the local machine to a remote SSH server. This tool establishes an SSH connection and transfers a local file to the specified remote path using SFTP protocol for reliable file transfer. Args: - host (string): SSH server hostname or IP address - port (number): SSH server port (default: 22) - username (string): SSH username - password (string): SSH password (optional if privateKey is provided) - privateKey (string): Path to private key file or private key content (optional) - timeout (number): Connection timeout in milliseconds (default: 30000) - local_path (string): Local file path to upload - remote_path (string): Destination path on the remote server - response_format (. It is categorised as a Write tool in the SSH MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH MCP Server 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 MCP Server. 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 MCP Server MCP server (lazyst/agent-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 →