ftp_sync · Ftp MCP: Risk & Policy

WHAT IT DOES

What ftp_sync does on Ftp

AI agents use ftp_sync to create or update resources in Ftp — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ftp environment.

WHY IT NEEDS A POLICY

Why ftp_sync needs a policy

ftp_sync transfers files from local to remote, creating or overwriting remote files. This is a Write operation at scale — it can overwrite many files across an entire project directory. It does not explicitly delete files not present locally (no mention of purge/mirror mode), so Destructive is not certain, but the blast radius is high given it deploys entire project folders.

From the tool's definition Deploy entire project folders using smart synchronization. Analyzes local and remote directory trees and only transfers files that have changed in size or modification date.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ftp_sync Rate-limited

ftp_sync 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": {
    "ftp_sync": {
      "limits": [
        {
          "counter": "ftp_sync_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ftp, so you can run agents against it safely.

FAQ

Questions about ftp_sync

What does the ftp_sync tool do? +

Deploy entire project folders using smart synchronization. Analyzes local and remote directory trees and only transfers files that have changed in size or modification date. Automatically respects .gitignore and .ftpignore. It is categorised as a Write tool in the Ftp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ftp_sync? +

Register the Ftp MCP server in PolicyLayer and add a rule for ftp_sync: 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 Ftp. Nothing to install.

What risk level is ftp_sync? +

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

Can I rate-limit ftp_sync? +

Yes. Add a rate_limit block to the ftp_sync 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 ftp_sync completely? +

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

ftp_sync is provided by the Ftp MCP server (kynlos/ftp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.