Find clickable elements
AI agents call chrome_get_interactive_elements to retrieve information from Chrome MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata about the DOM structure (which elements are clickable) but does not perform clicks, modify data, execute code, or trigger external operations. It is purely informational/read-only, similar to inspecting a web page. The low severity reflects minimal blast radius—an agent could only discover what elements exist on a page, not interact with them or cause side effects.
From the tool's definition Tool name is 'chrome_get_interactive_elements' and description states 'Find clickable elements' - this is a query/discovery operation that retrieves information about page elements without modifying state or executing actions.
Attacks that exploit this kind of access
Find clickable elements. It is categorised as a Read tool in the Chrome MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome MCP Server MCP server in PolicyLayer and add a rule for chrome_get_interactive_elements: 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 MCP Server. Nothing to install.
chrome_get_interactive_elements 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 chrome_get_interactive_elements 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 chrome_get_interactive_elements. 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.
chrome_get_interactive_elements is provided by the Chrome MCP Server MCP server (marie6789040106650/mcp-chrome-bk). 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 →