AI agents use batchUploadFiles 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.
This tool creates or modifies files on remote servers via SSH, which is a reversible Write operation. However, the severity is high because: (1) it operates on remote systems with potential for overwriting critical files, (2) batch operations amplify the blast radius, and (3) misconfigured paths or arguments could damage system integrity or expose sensitive data.
From the tool's definition Tool name 'batchUploadFiles' and description 'Uploads multiple local files to a remote server' indicate file creation/modification on remote systems.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batchUploadFiles 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 batchUploadFiles:
{
"version": "1",
"default": "deny",
"tools": {
"batchUploadFiles": {
"limits": [
{
"counter": "batchuploadfiles_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batchUploadFiles 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 multiple local files 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 batchUploadFiles: 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.
batchUploadFiles 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 batchUploadFiles 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 batchUploadFiles. 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.
batchUploadFiles 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.