chrome_type · Chrome MCP Stealth MCP: Risk & Policy

WHAT IT DOES

What chrome_type does on Chrome MCP Stealth

AI agents invoke chrome_type to trigger actions in Chrome MCP Stealth. 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 chrome_type needs a policy

Typing text into a browser constitutes an external operation that can submit forms, trigger searches, fill in authentication fields, or interact with web applications in ways whose effects depend entirely on the target element and content. The mention of 'Credential patterns blocked' implies the tool is aware of sensitive input risks.

From the tool's definition 'Type text' with 'Stealth: Gaussian delays + thinking pauses' and 'Credential patterns blocked' — triggers browser interaction by injecting keystrokes into web pages via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about chrome_type

What does the chrome_type tool do? +

Type text. Stealth: Gaussian delays + thinking pauses. Fast: instant. Credential patterns blocked. It is categorised as a Execute tool in the Chrome MCP Stealth MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chrome_type? +

Register the Chrome MCP Stealth 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 Chrome MCP Stealth. 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 Chrome MCP Stealth MCP server (riaan-fourie/chrome-mcp-stealth). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.