search_elements

Search for DOM elements matching a query string. Args: query: Search query (text content, tag name, or attribute) Returns: Search results with matching elements

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/search-elements.md

WHAT IT DOES

What search_elements does on Chrome Devtools

AI agents call search_elements 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 search_elements is rated Low

This tool retrieves and queries DOM elements without side effects. It performs a search operation that returns matching results, which is characteristic of Read category tools. The operation is non-destructive and involves no state changes, code execution, or external operations. The low severity reflects minimal blast radius—misuse would only return DOM information already accessible within the page context.

From the tool's definition Tool description states it 'Search[es] for DOM elements matching a query string' and 'Returns: Search results with matching elements'. The parameters indicate a read-only query operation with no modification or execution capabilities.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_elements 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 search_elements, this is the rule to start with:

search_elements Allowed

search_elements 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": {
    "search_elements": {}
  }
}

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 search_elements call is checked against it from then on.

FAQ

Questions about search_elements

What does the search_elements tool do? +

Search for DOM elements matching a query string. Args: query: Search query (text content, tag name, or attribute) Returns: Search results with matching elements. 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 search_elements? +

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

What risk level is search_elements? +

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

Can I rate-limit search_elements? +

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

How do I block search_elements completely? +

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

What MCP server provides search_elements? +

search_elements 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

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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