ftp_deploy · Ftp MCP: Risk & Policy

WHAT IT DOES

What ftp_deploy does on Ftp

AI agents invoke ftp_deploy to trigger actions in Ftp. 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.

WHY IT NEEDS A POLICY

Why ftp_deploy needs a policy

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. The 'pre-defined preset' mechanism means the tool orchestrates multiple sub-operations (likely including uploads, deletions per exclusion rules, and synchronization) based on configuration.

From the tool's definition ftp_deploy executes a pre-defined deployment preset that maps local folders to remote targets. The verb 'Execute' and the action of triggering a deployment operation with pre-configured rules indicates this runs an external operation whose effects (file…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ftp_deploy Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ftp_deploy": {
      "limits": [
        {
          "counter": "ftp_deploy_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_deploy

What does the ftp_deploy tool do? +

Execute a pre-defined deployment preset from .ftpconfig. This typically maps a specific local folder to a remote target with pre-configured exclusion rules. It is categorised as a Execute tool in the Ftp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ftp_deploy? +

Register the Ftp MCP server in PolicyLayer and add a rule for ftp_deploy: 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_deploy? +

ftp_deploy is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ftp_deploy? +

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

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

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