install_extension · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What install_extension does on Chrome Devtools

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

Installing a browser extension executes arbitrary privileged code within the browser context, granting it access to tabs, cookies, network requests, and potentially all browsing data. This is an Execute-category action with critical severity because a malicious or compromised extension path could lead to full browser compromise, credential theft, and persistent surveillance.

From the tool's definition 'Installs a Chrome extension from the given path' — installs executable browser extension code into a live Chrome browser

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_extension Rate-limited

install_extension 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": {
    "install_extension": {
      "limits": [
        {
          "counter": "install_extension_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 install_extension

What does the install_extension tool do? +

Installs a Chrome extension from the given path. 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 install_extension? +

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

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

Can I rate-limit install_extension? +

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

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

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

// THE FULL RECORD

install_extension is one line of Chrome Devtools's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →