Medium Risk

browser_fill_form

browser_fill_form

How to control browser_fill_form ↓

What browser_fill_form does on Playwright

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

Medium Risk

Why browser_fill_form needs a policy

Based on the name, this tool likely fills out and possibly submits web forms, which constitutes a Write action (creating or modifying data via form submission). However, depending on the form's purpose it could escalate to Financial or Destructive categories. The empty description lowers confidence.

From the tool's definition Tool name 'browser_fill_form' on Playwright MCP server; description is empty and uninformative.

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

How to control browser_fill_form

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

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

browser_fill_form 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 Playwright — 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.

Related tools and policies

Go deeper

Questions about browser_fill_form

What does the browser_fill_form tool do? +

browser_fill_form. It is categorised as a Write tool in the Playwright 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_fill_form? +

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

What risk level is browser_fill_form? +

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

Can I rate-limit browser_fill_form? +

Yes. Add a rate_limit block to the browser_fill_form 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_fill_form completely? +

Set action: deny in the PolicyLayer policy for browser_fill_form. 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_fill_form? +

browser_fill_form is provided by the Playwright MCP server (@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 Playwright tool call.

Start from Playwright, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

68 Playwright tools catalogued and risk-classified — across an index of 43,000+ 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.