chrome_fill_form

Fills multiple form fields in one shot in the current Google Chrome tab. Pass fields as a JSON object mapping CSS selector to value.

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/chrome-fill-form.md

WHAT IT DOES

What chrome_fill_form does on Local

AI agents invoke chrome_fill_form to trigger actions in Local. 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.

Parameter	Type	Required	Description
`fields`	string	Yes

Parameters from the server's own tool schema.

RISK

Why chrome_fill_form is rated High

This tool performs browser automation by filling form fields in an active Chrome tab. It triggers direct UI interactions that can submit data, authenticate, make purchases, or perform other consequential actions depending on what form is targeted.

From the tool's definition Fills multiple form fields in one shot in the current Google Chrome tab. Pass fields as a JSON object mapping CSS selector to value.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_fill_form safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_fill_form, this is the rule to start with:

chrome_fill_form Rate-limited

chrome_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": {
    "chrome_fill_form": {
      "limits": [
        {
          "counter": "chrome_fill_form_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every chrome_fill_form call is checked against it from then on.

FAQ

Questions about chrome_fill_form

What does the chrome_fill_form tool do? +

Fills multiple form fields in one shot in the current Google Chrome tab. Pass fields as a JSON object mapping CSS selector to value. It is categorised as a Execute tool in the Local MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does chrome_fill_form accept? +

chrome_fill_form accepts 1 parameter: fields. Required: fields. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on chrome_fill_form? +

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

What risk level is chrome_fill_form? +

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

Can I rate-limit chrome_fill_form? +

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

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

chrome_fill_form is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools → High-risk tools on this server →

Across the catalogue

browser_fill on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →