fill_form · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What fill_form does on Chrome Devtools

AI agents invoke fill_form to trigger actions in Chrome Devtools. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why fill_form needs a policy

Filling forms in a live browser is an external operation whose effects depend on arguments. It can populate login forms, payment fields, or any other form, potentially triggering submissions with side effects. This goes beyond simple Write as it executes browser actions against live web pages, and misuse could lead to unintended data submission or account actions.

From the tool's definition 'Fill out multiple form elements at once' — triggers browser interactions that modify form state and can submit data to external systems

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fill_form Rate-limited

fill_form stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fill_form": {
      "limits": [
        {
          "counter": "fill_form_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Chrome Devtools, so you can run agents against it safely.

FAQ

Questions about fill_form

What does the fill_form tool do? +

Fill out multiple form elements at once. 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 fill_form? +

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

What risk level is fill_form? +

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

Can I rate-limit fill_form? +

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

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

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

// THE FULL RECORD

fill_form is one line of Chrome Devtools's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →