AI agents use ssh_upload to create or update resources in MCP File Edit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP File Edit environment.
SSH upload transfers files to remote systems, which creates or modifies data on those systems. This is a Write operation (reversible), but carries high severity due to the remote execution context and potential to modify critical system files or configurations. Confidence is slightly lowered due to empty tool description, but the name and server-level documentation provide sufficient context.
From the tool's definition Tool name 'ssh_upload' indicates file transfer via SSH to remote systems. Server description mentions 'SSH transfers' as a capability. No detailed description provided, but upload operations create or modify files on remote targets.
Documented attack patterns abuse exactly the kind of access ssh_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP File Edit, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_upload:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_upload": {
"limits": [
{
"counter": "ssh_upload_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ssh_upload 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.
ssh_upload. It is categorised as a Write tool in the MCP File Edit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP File Edit MCP server in PolicyLayer and add a rule for ssh_upload: 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 File Edit. Nothing to install.
ssh_upload 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 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. 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 is provided by the MCP File Edit MCP server (patrickomatik/mcp-file-edit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP File Edit, 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.
32 MCP File Edit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.