Download a file from the IBM i to the local system.
AI agents call download_file to retrieve information from Ibmi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves/extracts data (a file) from the IBM i system to the local system. It has no side effects on the source data—the file remains unchanged on IBM i. This is a read operation. Severity is low because file downloads have minimal blast radius unless the downloaded content itself is sensitive, which depends on access controls and file contents rather than the tool's inherent capability.
From the tool's definition Tool name is 'download_file' with description 'Download a file from the IBM i to the local system.' The operation retrieves data from the remote system without modification or deletion.
Documented attack patterns abuse exactly the kind of access download_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ibmi, and nothing reaches the server without passing your rules. This is the rule we recommend for download_file:
{
"version": "1",
"default": "deny",
"tools": {
"download_file": {}
}
} download_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Download a file from the IBM i to the local system. It is categorised as a Read tool in the Ibmi MCP Server, which means it retrieves data without modifying state.
Register the Ibmi MCP server in PolicyLayer and add a rule for download_file: 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 Ibmi. Nothing to install.
download_file 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 download_file 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 download_file. 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.
download_file is provided by the Ibmi MCP server (whitehornltd/ibmi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ibmi, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Ibmi tools catalogued and risk-classified — across an index of 43,000+ MCP servers.