chrome_query_selector_all
Runs document.querySelectorAll in the current Google Chrome tab and returns a compact summary of each match.
This record as markdown: /tools/com-local-mcp-local-mcp/chrome-query-selector-all.md
What chrome_query_selector_all does on Local
AI agents call chrome_query_selector_all to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
selector | string | Yes |
Parameters from the server's own tool schema.
Why chrome_query_selector_all is rated Low
querySelectorAll is a read-only DOM query function that retrieves and summarizes matching elements from the page structure. It has no side effects—it does not execute scripts, modify the DOM, trigger actions, or move data. The tool merely returns information about page structure, making it a Read operation with low risk.
From the tool's definition Tool description states it 'Runs document.querySelectorAll in the current Google Chrome tab and returns a compact summary of each match.' querySelectorAll is a DOM query operation that retrieves elements without modifying them.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs chrome_query_selector_all safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For chrome_query_selector_all, this is the rule to start with:
chrome_query_selector_all 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 Local, apply this rule, and every chrome_query_selector_all call is checked against it from then on.
Questions about chrome_query_selector_all
Runs document.querySelectorAll in the current Google Chrome tab and returns a compact summary of each match. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
chrome_query_selector_all accepts 2 parameters: limit, selector. Required: selector. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for chrome_query_selector_all: 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 Local. Nothing to install.
chrome_query_selector_all 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_query_selector_all 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_query_selector_all. 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_query_selector_all is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue