Upload a local file from an allowed local root to the remote server via SFTP
AI agents use ssh_upload_file to create or update resources in SSH Remote MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH Remote MCP Server environment.
This tool writes data to a remote server via file upload. While the upload itself is reversible (files can be deleted), the severity is high because: (1) it modifies remote system state, (2) the blast radius depends on what files are uploaded and their permissions—malicious files could compromise system security, (3) it operates within the context of an SSH server that enables broad command execution capabilities.
From the tool's definition Tool description explicitly states 'Upload a local file...to the remote server via SFTP'. The action creates or modifies data on a remote system by transferring a file, which is reversible (the file can be deleted or overwritten).
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access ssh_upload_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_upload_file": {
"limits": [
{
"counter": "ssh_upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} ssh_upload_file stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload a local file from an allowed local root to the remote server via SFTP. It is categorised as a Write tool in the SSH Remote MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH Remote 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 Remote 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 Remote MCP Server MCP server (nqmn/adremote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH Remote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 SSH Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.