AI agents use uploadFile 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.
Uploading files is a Write operation (creates/modifies data). Severity is medium rather than high because: (1) the operation is reversible (file can be deleted), (2) impact depends on what file is uploaded and where, and (3) it requires prior SSH connection authorization. Confidence is high given the explicit description clearly indicates file creation/modification on remote systems.
From the tool's definition Tool description states 'Uploads a local file to a remote server.' This creates or modifies data on the remote system. While reversible, the uploaded file could overwrite existing data or be malicious content placed on a production server.
Documented attack patterns abuse exactly the kind of access uploadFile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ssh, and nothing reaches the server without passing your rules. This is the rule we recommend for uploadFile:
{
"version": "1",
"default": "deny",
"tools": {
"uploadFile": {
"limits": [
{
"counter": "uploadfile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}uploadFile 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.
Uploads a local file to a remote server. 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 uploadFile: 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.
uploadFile 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 uploadFile 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 uploadFile. 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.
uploadFile is provided by the Mcp Ssh MCP server (shuakami/mcp-ssh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Mcp Ssh tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
23 Mcp Ssh tools catalogued and risk-classified — across an index of 42,500+ MCP servers.