Copy a single file between local and remote server via SFTP (simpler than rsync for single files)
AI agents use scp_copy to create or update resources in SSH MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SSH MCP Server environment.
The scp_copy tool performs file transfer operations that result in file creation or modification on the destination system (either local or remote). This is a Write operation—reversible but consequential. It is not Destructive because it does not delete or overwrite existing files (SCP typically fails if destination exists). It is not Execute because the tool itself does not run arbitrary commands—it transfers files.
From the tool's definition Tool description states 'Copy a single file between local and remote server via SFTP', indicating file creation/modification on either local or remote system.
Documented attack patterns abuse exactly the kind of access scp_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 scp_copy:
{
"version": "1",
"default": "deny",
"tools": {
"scp_copy": {
"limits": [
{
"counter": "scp_copy_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} scp_copy 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.
Copy a single file between local and remote server via SFTP (simpler than rsync for single files). It is categorised as a Write tool in the SSH MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for scp_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.
scp_copy 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 scp_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 scp_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.
scp_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.