reload_extension · Chrome Devtools MCP: Risk & Policy

WHAT IT DOES

What reload_extension does on Chrome Devtools

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

Reloading a Chrome extension triggers an external browser operation that restarts the extension's runtime, potentially interrupting active operations, clearing extension state, and affecting any functionality the extension provides. This is an action that executes an operation in the browser environment rather than simply reading or writing data.

From the tool's definition Reloads an unpacked Chrome extension by its ID

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reload_extension Rate-limited

reload_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": {
    "reload_extension": {
      "limits": [
        {
          "counter": "reload_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 reload_extension

What does the reload_extension tool do? +

Reloads an unpacked Chrome extension by its ID. 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 reload_extension? +

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

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

Can I rate-limit reload_extension? +

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

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

reload_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.