install_extension
Installs a Chrome extension from the given path.
This record as markdown: /tools/async23-chrome-devtools-mcp/install-extension.md
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 install_extension is rated High
Installing a Chrome extension can grant the extension access to all browsing data, network requests, page contents, and more. A malicious or unvetted extension could exfiltrate data, manipulate web pages, intercept credentials, or perform destructive/financial actions. This is an Execute-class action with critical blast radius since the extension runs persistently in the browser with elevated privileges.
From the tool's definition 'Installs a Chrome extension from the given path' — installing an extension executes arbitrary browser-level code with broad permissions
Attacks that exploit this kind of access
The rule that runs install_extension 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 install_extension, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every install_extension call is checked against it from then on.
Questions about install_extension
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.
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.
install_extension is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
install_extension 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.
More on Chrome Devtools, and thousands of servers like it.
Across the catalogue