AI agents use ftp_batch_upload 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.
This tool creates or modifies files on remote servers by uploading local files. It is reversible (files can be deleted or overwritten later), so it falls under Write rather than Destructive.
From the tool's definition Tool name 'ftp_batch_upload' and description 'Upload a collection of local files to remote destinations' explicitly indicates creation/modification of data on remote systems via FTP/SFTP.
Attacks that exploit this kind of access
Upload a collection of local files to remote destinations in a single operation. HIGHLY RECOMMENDED for multiple files to minimize connection handshaking overhead and drastically improve performance. 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.
Register the Ftp MCP server in PolicyLayer and add a rule for ftp_batch_upload: 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.
ftp_batch_upload is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ftp_batch_upload 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.
Set action: deny in the PolicyLayer policy for ftp_batch_upload. 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.
ftp_batch_upload 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.
ftp_batch_upload is one line of Ftp's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →