High Risk →

upload_file

Upload a file through a form input

Can upload sensitive files

Part of the Chrome DevTools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke upload_file to trigger processes or run actions in Chrome DevTools. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

upload_file can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

chrome-devtools.yaml
tools:
  upload_file:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Chrome DevTools policy for all 29 tools.

Tool Name upload_file
Category Execute
Risk Level High

View all 29 tools →

Agents calling execute-class tools like upload_file have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

upload_file is one of the high-risk operations in Chrome DevTools. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the upload_file tool do? +

Upload a file through a form input. It is categorised as a Execute tool in the Chrome DevTools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on upload_file? +

Add a rule in your Intercept YAML policy under the tools section for upload_file. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Chrome DevTools MCP server.

What risk level is upload_file? +

upload_file is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit upload_file? +

Yes. Add a rate_limit block to the upload_file rule in your Intercept 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 Intercept 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 (@ChromeDevTools/chrome-devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Chrome DevTools

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.