AI agents call ftp_batch_download to retrieve information from Ftp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval only. Downloading files is a read operation with no side effects on the source system. While bulk downloads could theoretically involve large data transfers, the operation itself is non-destructive and non-modifying. The low severity reflects that misuse would primarily result in unauthorized data access rather than system compromise or data loss.
From the tool's definition Tool description states 'Download a selection of remote files to local destinations' - a read operation that retrieves data from remote servers without modifying, deleting, or executing anything on the remote or local system.
Attacks that exploit this kind of access
Download a selection of remote files to local destinations. HIGHLY RECOMMENDED for bulk downloads to leverage stable socket persistence. It is categorised as a Read tool in the Ftp MCP Server, which means it retrieves data without modifying state.
Register the Ftp MCP server in PolicyLayer and add a rule for ftp_batch_download: 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_download is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ftp_batch_download 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_download. 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_download 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →