// SCAN REPORT

Ftp

28 tools. 14 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

14 can modify or destroy data

14 read-only

28 tools total

Community server · catalogue entry verified 30/06/2026

How to control Ftp ↓

TOOL MAP

What Ftp exposes to your agents

Read (14) Write / Execute (12) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Ftp tools

Destructive · High ftp_delete This tool irreversibly deletes data without possibility of recovery, fitting the Destructive category definition. Destructive · High ftp_rmdir Directory deletion is inherently destructive—it cannot be undone and removes data with no recovery path. Execute · High ftp_deploy While ftp_deploy facilitates file transfers, it is fundamentally an Execute tool because it triggers a compound deployment operation rather than a simple read or write. Write · High ftp_sync ftp_sync transfers files from local to remote, creating or overwriting remote files.

14 of Ftp's 28 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Ftp

PolicyLayer is an MCP gateway — it sits between your AI agents and Ftp, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "ftp_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "ftp_batch_upload": {
    "limits": [
      {
        "counter": "ftp_batch_upload_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "ftp_analyze_workspace": {
    "limits": [
      {
        "counter": "ftp_analyze_workspace_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Ftp — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FTP →

Instant setup, no code required.

FULL CATALOGUE

All 28 Ftp tools

DESTRUCTIVE 2 tools

Destructive ftp_delete Permanently remove a file from the remote server. Use with caution. Destructive ftp_rmdir Delete a directory from the remote server.

EXECUTE 1 tools

Execute ftp_deploy Execute a pre-defined deployment preset from .ftpconfig. This typically maps a specific local folder to a remo

WRITE 11 tools

Write ftp_batch_upload Upload a collection of local files to remote destinations in a single operation. HIGHLY RECOMMENDED for multip Write ftp_chmod Change remote file permissions. CRITICAL: Only supported on SFTP connections. Write ftp_connect Establish or switch the active connection to a specific remote server profile defined in your .ftpconfig (e.g. Write ftp_copy Directly duplicate a file on the remote server without downloading and re-uploading. CRITICAL: Only supported Write ftp_mkdir Create a new directory structure on the remote server. Supports nested creation (mkdir -p). Write ftp_patch_file Apply a Unified Diff patch to a remote file. RECOMMENDED: Use this instead of ftp_put_contents for updating ex Write ftp_put_contents Write raw text directly to a remote destination. Best for creating NEW files. For modifying existing files, pr Write ftp_rename Move or rename files and directories on the remote server. Write ftp_rollback Undo a previous file mutation by restoring it from a system-generated snapshot. This provides safety during co Write ftp_sync Deploy entire project folders using smart synchronization. Analyzes local and remote directory trees and only Write ftp_upload Standard single-file transport to the remote server. For bulk transfers, favor ftp_batch_upload.

READ 14 tools

Read ftp_analyze_workspace Introspect the remote directory to identify technical environments (e.g., Node.js, PHP, Python) and read depen Read ftp_batch_download Download a selection of remote files to local destinations. HIGHLY RECOMMENDED for bulk downloads to leverage Read ftp_disk_space Query the remote server for available disk space. CRITICAL: Only available on SFTP connections. Read ftp_download Standard single-file transport from the remote server. For bulk downloads, favor ftp_batch_download. Read ftp_exists Check for the existence of a file or folder without performing heavy file operations. Use this for conditional Read ftp_get_contents Read the source text of a remote file. CRITICAL: For large files, use Read ftp_list List files and directories in a remote path. Use Read ftp_list_deployments List all available deployment presets from .ftpconfig Read ftp_list_transactions Expose all recent mutations currently stored in the system Read ftp_probe_capabilities Scan the remote server to determine supported filesystem features (e.g., chmod availability, symlink support, Read ftp_search Advanced remote file search. Supports finding files by name (wildcards), extension, or content regex (grep-lik Read ftp_stat Retrieve comprehensive metadata for a remote property, including size, modification timestamps, and UNIX permi Read ftp_telemetry Retrieve internal performance metrics, including average latency, connection pool health, and total processed Read ftp_tree Generate a complete recursive directory map. Use this to visualize project structure, but be cautious with

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Ftp

Can an AI agent delete data through the Ftp MCP server? +

Yes. The Ftp server exposes 2 destructive tools including ftp_delete, ftp_rmdir. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Ftp? +

The Ftp server has 11 write tools including ftp_batch_upload, ftp_chmod, ftp_connect. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Ftp.

How many tools does the Ftp MCP server expose? +

28 tools across 4 categories: Destructive, Execute, Read, Write. 14 are read-only. 14 can modify, create, or delete data.

How do I enforce a policy on Ftp? +

Register the Ftp MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Ftp tool call.

Deterministic rules across all 28 Ftp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FTP →

Instant setup, no code required.

28 Ftp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.