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 Opera DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries extension information without modifying, executing, or deleting anything. It has a minimal blast radius—an AI agent cannot cause harm by reading extension metadata. The data is already available to the browser and the user can see installed extensions in the UI. This is a classic Read operation (fetch/query).
From the tool's definition Tool name is 'list_extensions' and description states it 'Lists all the Chrome extensions installed in the browser' with retrieval of metadata (name, ID, version, enabled status).
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 Opera DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the Opera 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 Opera DevTools MCP. 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 Opera DevTools MCP server (operasoftware/opera-devtools-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 →