upload_file

Upload a file through a provided element.

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/upload-file.md

WHAT IT DOES

What upload_file does on Chrome Devtools

AI agents use upload_file to create or update resources in Chrome Devtools, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Chrome Devtools environment.

RISK

Why upload_file is rated Medium

File upload is a reversible write operation that creates or modifies data on a server. It does not delete, destroy, or move financial assets. However, severity is elevated to 'medium' because uncontrolled file uploads in an undetected browser automation context could be exploited to upload malicious files, bypass security controls, or inject content into systems.

From the tool's definition Tool description states 'Upload a file through a provided element.' This performs a file upload action—a data modification operation that writes data to a remote system via a web interface.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs upload_file safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "upload_file": {
      "limits": [
        {
          "counter": "upload_file_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every upload_file call is checked against it from then on.

FAQ

Questions about upload_file

What does the upload_file tool do? +

Upload a file through a provided element. It is categorised as a Write tool in the Chrome Devtools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload_file? +

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. Nothing to install.

What risk level is upload_file? +

upload_file is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload_file? +

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.

How do I block upload_file completely? +

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.

What MCP server provides upload_file? +

upload_file is provided by the Chrome Devtools MCP server (@async23/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →