transfer_file

A write tool on the SSH MCP server.

SERVERSSH MCP Server SOURCEbhayanak/ssh-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bhayanak-ssh-mcp-server/transfer-file.md

WHAT IT DOES

What transfer_file does on SSH MCP Server

AI agents use transfer_file 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.

RISK

Why transfer_file is rated Medium

The tool name 'transfer_file' strongly implies transferring files to/from remote servers (analogous to SCP/SFTP). This is a Write operation as it creates or modifies data on remote systems. The description is empty, which lowers confidence. Severity is high because misuse could overwrite critical system files on remote Linux servers or exfiltrate sensitive data.

From the tool's definition Tool name 'transfer_file' on an SSH MCP Server that manages remote Linux servers

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_file, this is the rule to start with:

transfer_file Rate-limited

transfer_file 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_file": {
      "limits": [
        {
          "counter": "transfer_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every transfer_file call is checked against it from then on.

FAQ

Questions about transfer_file

What does the transfer_file tool do? +

transfer_file is a write tool on the SSH MCP Server MCP server. 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.

How do I enforce a policy on transfer_file? +

Register the SSH MCP Server MCP server in PolicyLayer and add a rule for transfer_file: 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.

What risk level is transfer_file? +

transfer_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_file? +

Yes. Add a rate_limit block to the transfer_file 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.

How do I block transfer_file completely? +

Set action: deny in the PolicyLayer policy for transfer_file. 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.

What MCP server provides transfer_file? +

transfer_file is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SSH MCP Server, and thousands of servers like it.

This server

All 23 SSH MCP Server tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →