Upload files to a file input element on the page. Pass intent=
AI agents invoke file_upload to trigger actions in OpenChrome. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Uploading files to a web page is a browser-executed action with external side effects: it sends data to a remote service, potentially exposing sensitive local files. The description is truncated ('Pass intent='), reducing confidence slightly, but the core action is clearly an Execute-category browser automation operation.
From the tool's definition 'Upload files to a file input element on the page' — triggers a browser action that transfers files to an external page/service
Documented attack patterns abuse exactly the kind of access file_upload gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for file_upload:
{
"version": "1",
"default": "deny",
"tools": {
"file_upload": {
"limits": [
{
"counter": "file_upload_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}file_upload stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Upload files to a file input element on the page. Pass intent=. It is categorised as a Execute tool in the OpenChrome MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenChrome MCP server in PolicyLayer and add a rule for file_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 OpenChrome. Nothing to install.
file_upload is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the file_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 file_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.
file_upload is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.