type_text

Type text using keyboard into a previously focused input

SERVERChrome Devtools SOURCE@async23/chrome-devtools-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/async23-chrome-devtools-mcp/type-text.md

WHAT IT DOES

What type_text does on Chrome Devtools

AI agents invoke type_text 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.

RISK

Why type_text is rated High

This tool simulates keyboard input into a browser context, which is an external browser action. It can trigger form submissions, JavaScript event handlers, or other side effects depending on the target element and the text typed. It's an Execute-category action as it triggers external operations in the browser whose effects depend on the arguments provided.

From the tool's definition Type text using keyboard into a previously focused input

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs type_text safely

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

type_text Rate-limited

type_text 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": {
    "type_text": {
      "limits": [
        {
          "counter": "type_text_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 Chrome Devtools, apply this rule, and every type_text call is checked against it from then on.

FAQ

Questions about type_text

What does the type_text tool do? +

Type text using keyboard into a previously focused input. 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 type_text? +

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

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

Can I rate-limit type_text? +

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

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

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

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 50 Chrome Devtools 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 →