chrome_type

Sets the value of an input/textarea matching a CSS selector in the current Google Chrome tab and fires input/change events.

SERVERLocal SOURCElocal-mcp

High RISK CLASS

Category Execute

Parameters 32 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-type.md

WHAT IT DOES

What chrome_type does on Local

AI agents invoke chrome_type 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
`clear`	boolean	—
`value`	string	Yes
`selector`	string	Yes

Parameters from the server's own tool schema.

RISK

Why chrome_type is rated High

This tool actively manipulates the browser DOM by setting input values and firing events, constituting a browser action with real side effects. It can be used to fill forms, trigger handlers, and interact with web applications in ways that could lead to unintended submissions or data entry, placing it in the Execute category.

From the tool's definition Sets the value of an input/textarea matching a CSS selector in the current Google Chrome tab and fires input/change events

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs chrome_type 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_type, this is the rule to start with:

chrome_type Rate-limited

chrome_type 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_type": {
      "limits": [
        {
          "counter": "chrome_type_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_type call is checked against it from then on.

FAQ

Questions about chrome_type

What does the chrome_type tool do? +

Sets the value of an input/textarea matching a CSS selector in the current Google Chrome tab and fires input/change events. 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_type accept? +

chrome_type accepts 3 parameters: clear, value, selector. Required: value, selector. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on chrome_type? +

Register the Local MCP server in PolicyLayer and add a rule for chrome_type: 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_type? +

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

Can I rate-limit chrome_type? +

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

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

chrome_type 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

qt_type on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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