Upload a file from the local system to the IBM i.
AI agents use upload_file to create or update resources in Ibmi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ibmi environment.
This tool uploads files to IBM i, which is a data creation/modification action. It is not destructive (files can be deleted), not financial, and not execute-level arbitrary code (though uploaded files could potentially be executed separately).
From the tool's definition Tool description states 'Upload a file from the local system to the IBM i' – this creates or modifies data on the IBM i system. The tool transfers files to the remote IBM i system, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access upload_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 upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"upload_file": {
"limits": [
{
"counter": "upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_file 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.
Free to start. No card required.
Upload a file from the local system to the IBM i. It is categorised as a Write tool in the Ibmi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ibmi MCP server in PolicyLayer and add a rule for upload_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.
upload_file 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 upload_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 upload_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.
upload_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.