Upload a file to the remote server
AI agents use ssh_upload_file to create or update resources in SSH MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH MCP environment.
This tool creates or modifies data on a remote server by uploading files. While reversible (files can be deleted), the ability to upload arbitrary files to a remote system poses significant risk—malicious files could compromise the server, overwrite critical configurations, or introduce backdoors.
From the tool's definition Tool name 'ssh_upload_file' and description 'Upload a file to the remote server' indicate creation/modification of files on a remote system.
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 MCP, 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 file to the remote server. It is categorised as a Write tool in the SSH MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH 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. 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 (mixelpixx/ssh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH MCP, 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.
6 SSH MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.