Upload a local file to the remote SSH server using SFTP.
AI agents use upload-file to create or update resources in TermSSH MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TermSSH MCP environment.
The tool enables creation and modification of files on a remote system via SFTP. While not irreversibly destructive (files can be deleted or modified later), the ability to upload arbitrary files to a remote server is a high-severity Write risk, as a compromised AI agent could upload malicious scripts, credentials, or overwrite critical configuration files.
From the tool's definition The tool description states it 'Upload[s] a local file to the remote SSH server using SFTP,' which creates or modifies files on a remote system. This is a Write operation—it creates new files or overwrites existing ones on the remote server.
Attacks that exploit this kind of access
Upload a local file to the remote SSH server using SFTP. It is categorised as a Write tool in the TermSSH MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TermSSH 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 TermSSH MCP. 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 TermSSH MCP server (rayss868/termssh-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 →