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 performs information retrieval only—it discovers and returns data about interactive elements on a webpage. It has no side effects, does not execute code, does not modify data, and does not perform destructive operations. While it could be used to gather information for subsequent malicious actions (like clicking), the tool itself is purely Read category.
From the tool's definition The tool description states 'Find clickable elements' and the name indicates 'get' (retrieve) functionality. This is a query/discovery operation that retrieves information about DOM elements without modifying state or triggering 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 (standbyme626/mcp-chrome). 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 →