Query the browser in real-time to inspect ANY element by CSS selector — even deeply nested ones. Sends a command to the browser to capture the element
AI agents call live_query_element to retrieve information from Mcp Browser Lens without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves element information from the DOM via CSS selector inspection. It performs no mutation, execution of external code, deletion, or financial operations. The ability to query 'ANY element' does not elevate risk because the operation is read-only—it extracts existing UI state and properties.
From the tool's definition Tool description states it 'query the browser in real-time to inspect ANY element by CSS selector' and 'capture the element'. The verb 'query' and 'inspect' indicate data retrieval without modification.
Attacks that exploit this kind of access
Query the browser in real-time to inspect ANY element by CSS selector — even deeply nested ones. Sends a command to the browser to capture the element. It is categorised as a Read tool in the Mcp Browser Lens MCP Server, which means it retrieves data without modifying state.
Register the Mcp Browser Lens MCP server in PolicyLayer and add a rule for live_query_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 Mcp Browser Lens. Nothing to install.
live_query_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 live_query_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 live_query_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.
live_query_element is provided by the Mcp Browser Lens MCP server (nano-step/mcp-browser-lens). 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 →