upload_file
Upload a file through a provided element.
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/upload-file.md
What upload_file does on Chrome DevTools MCP
AI agents use upload_file to create or update resources in Chrome DevTools MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome DevTools MCP environment.
Why upload_file is rated Medium
This tool creates or writes data to the system via browser file upload mechanism. It is reversible (files can be deleted) and does not inherently destroy data or execute arbitrary code on the host—it simply facilitates file upload through DOM interaction. While it could be misused to upload malicious content to a vulnerable server, the tool itself is a Write action.
From the tool's definition Tool name is 'upload_file' and description states it 'Upload a file through a provided element.' This performs file upload via browser automation, which modifies the state of the browser/web application by adding a file to the system.
Attacks that exploit this kind of access
The rule that runs upload_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For upload_file, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome DevTools MCP, apply this rule, and every upload_file call is checked against it from then on.
Questions about upload_file
Upload a file through a provided element. It is categorised as a Write tool in the Chrome DevTools MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Chrome DevTools 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 Chrome DevTools MCP. 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 Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome DevTools, and thousands of servers like it.
This server
Across the catalogue