Lists all the Chrome extensions installed in the browser. This includes their name, ID, version, and enabled status.
AI agents call list_extensions to retrieve information from Chrome Devtools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves browser extension metadata without modifying or executing anything. While it is a Read category tool by primary function, the severity is elevated to medium because the list of installed extensions can reveal sensitive information about the user's security posture, privacy tools, banking extensions, or other extensions that indicate vulnerabilities or high-value targets for an attacker.
From the tool's definition Tool description states it 'Lists all the Chrome extensions installed in the browser' with name, ID, version, and enabled status. The verb 'lists' and action of retrieving extension information without modification indicates a read operation.
Attacks that exploit this kind of access
Lists all the Chrome extensions installed in the browser. This includes their name, ID, version, and enabled status. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for list_extensions: 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.
list_extensions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_extensions 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 list_extensions. 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.
list_extensions is provided by the Chrome Devtools MCP server (zhang77-x/chrpme_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →