query_selector

Execute querySelector on a DOM node. Args: node_id: Target node ID to query within selector: CSS selector string Returns: Node ID of the matching element

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/query-selector.md

WHAT IT DOES

What query_selector does on Chrome Devtools

AI agents call query_selector to retrieve information from Chrome Devtools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why query_selector is rated Low

querySelector is a read-only DOM query operation that finds elements matching a CSS selector. It has no side effects — it simply returns a node ID of the matching element without modifying the page, executing scripts, or causing any state changes.

From the tool's definition Execute querySelector on a DOM node... Returns: Node ID of the matching element

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query_selector safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome Devtools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query_selector, this is the rule to start with:

query_selector Allowed

query_selector is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_selector": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Chrome Devtools, apply this rule, and every query_selector call is checked against it from then on.

FAQ

Questions about query_selector

What does the query_selector tool do? +

Execute querySelector on a DOM node. Args: node_id: Target node ID to query within selector: CSS selector string Returns: Node ID of the matching element. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_selector? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for query_selector: 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 Devtools. Nothing to install.

What risk level is query_selector? +

query_selector is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_selector? +

Yes. Add a rate_limit block to the query_selector 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.

How do I block query_selector completely? +

Set action: deny in the PolicyLayer policy for query_selector. 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.

What MCP server provides query_selector? +

query_selector is provided by the Chrome Devtools MCP server (benjaminr/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Chrome Devtools, and thousands of servers like it.

This server

All 47 Chrome Devtools tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →