ftp_rename · Ftp MCP: Risk & Policy

WHAT IT DOES

What ftp_rename does on Ftp

AI agents use ftp_rename 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_rename needs a policy

Renaming and moving files are Write operations: they modify the remote filesystem state but remain reversible (the file can be renamed or moved back). This is less severe than Destructive (which would be irreversible deletion) and more severe than Read. Medium severity reflects that an agent error could reorganize critical server structure, but the operation is undoable.

From the tool's definition Tool description states 'Move or rename files and directories on the remote server' — these are reversible modifications to file metadata and location that do not permanently destroy data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ftp_rename Rate-limited

ftp_rename 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_rename": {
      "limits": [
        {
          "counter": "ftp_rename_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_rename

What does the ftp_rename tool do? +

Move or rename files and directories on the remote server. 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_rename? +

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

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

Can I rate-limit ftp_rename? +

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

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

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