fill · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What fill does on Chrome Devtools

AI agents invoke fill 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 needs a policy

Filling in form fields is a browser automation action that produces side effects in a live browser session. It can submit credentials, alter form state, or trigger dynamic page behavior. This falls under Execute as it performs an external browser operation whose effects depend on the arguments provided.

From the tool's definition 'Type text into an input, text area or select an option from a <select> element' — triggers browser interaction/automation actions in a live Chrome browser

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fill Rate-limited

fill 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": {
      "limits": [
        {
          "counter": "fill_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

What does the fill tool do? +

Type text into an input, text area or select an option from a <select> element. 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? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for fill: 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? +

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

Can I rate-limit fill? +

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

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

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