Medium Risk

browser_file_upload

Upload one or multiple files to file input

How to control browser_file_upload ↓

AI agents use browser_file_upload to create or update resources in Fast Playwright MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fast Playwright MCP environment.

Medium Risk

This tool uploads files to a file input element in the browser, which is a write operation that sends data to a remote service. It has high severity because an AI agent could misuse it to upload sensitive files, malware, or large amounts of data to arbitrary web endpoints without user awareness.

From the tool's definition Upload one or multiple files to file input

Documented attack patterns abuse exactly the kind of access browser_file_upload gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Fast Playwright MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_file_upload:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_file_upload": {
      "limits": [
        {
          "counter": "browser_file_upload_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

browser_file_upload 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.

  1. Create a free account and register Fast Playwright MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the browser_file_upload tool do? +

Upload one or multiple files to file input. It is categorised as a Write tool in the Fast Playwright MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on browser_file_upload? +

Register the Fast Playwright MCP server in PolicyLayer and add a rule for browser_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 Fast Playwright MCP. Nothing to install.

What risk level is browser_file_upload? +

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

Can I rate-limit browser_file_upload? +

Yes. Add a rate_limit block to the browser_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.

How do I block browser_file_upload completely? +

Set action: deny in the PolicyLayer policy for browser_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.

What MCP server provides browser_file_upload? +

browser_file_upload is provided by the Fast Playwright MCP server (tontoko/fast-playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fast Playwright MCP tool call.

Deterministic rules across all 34 Fast Playwright MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

34 Fast Playwright MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.