chrome_smart_locate_element
Use Playwright-inspired smart element location strategies to find elements with high precision
This record as markdown: /tools/2019-02-18-mcx/chrome-smart-locate-element.md
What chrome_smart_locate_element does on Chrome Feedback
AI agents call chrome_smart_locate_element to retrieve information from Chrome Feedback without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why chrome_smart_locate_element is rated Low
This tool queries the DOM to locate elements but does not execute code, modify state, or trigger side effects. It is a read-only inspection capability similar to page analysis tools. The 'smart locate' capability carries minimal risk—the worst case is incorrect element identification, which would fail downstream actions rather than cause direct harm.
From the tool's definition Tool description states it 'find[s] elements with high precision' using location strategies. The verb 'find' and 'locate' indicate information retrieval without modification. No mention of modifying, executing, or destructing data.
Attacks that exploit this kind of access
The rule that runs chrome_smart_locate_element safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Feedback, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_smart_locate_element, this is the rule to start with:
chrome_smart_locate_element is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Feedback, apply this rule, and every chrome_smart_locate_element call is checked against it from then on.
Questions about chrome_smart_locate_element
Use Playwright-inspired smart element location strategies to find elements with high precision. It is categorised as a Read tool in the Chrome Feedback MCP Server, which means it retrieves data without modifying state.
Register the Chrome Feedback MCP server in PolicyLayer and add a rule for chrome_smart_locate_element: 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 Feedback. Nothing to install.
chrome_smart_locate_element 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_smart_locate_element 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_smart_locate_element. 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_smart_locate_element is provided by the Chrome Feedback MCP server (2019-02-18/mcx). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome Feedback, and thousands of servers like it.
This server
Across the catalogue