Copy files/directories between local and remote server via rsync (best for directories or large transfers)
AI agents invoke rsync_copy to trigger actions in SSH MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
rsync_copy executes the rsync command to transfer files between systems. While it is primarily a file-transfer operation, rsync can overwrite destination files, delete files at the destination (with --delete flag), and execute across remote systems via SSH.
From the tool's definition Copy files/directories between local and remote server via rsync
Documented attack patterns abuse exactly the kind of access rsync_copy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rsync_copy:
{
"version": "1",
"default": "deny",
"tools": {
"rsync_copy": {
"limits": [
{
"counter": "rsync_copy_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} rsync_copy stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Copy files/directories between local and remote server via rsync (best for directories or large transfers). It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for rsync_copy: 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 Server. Nothing to install.
rsync_copy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the rsync_copy 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 rsync_copy. 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.
rsync_copy is provided by the SSH MCP Server MCP server (kinothe-kafkaesque/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH 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.
15 SSH MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.