Low Risk

search_dom_elements

Search for DOM elements by type, content, keywords, or attributes. Returns matching elements with their paths for further navigation.

How to control search_dom_elements ↓

AI agents call search_dom_elements to retrieve information from ZMCPTools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool queries the DOM structure to find and return element information. It is a read-only search operation that retrieves data about page elements without side effects. The tool does not execute scripts, modify content, navigate, or trigger actions—it only provides visibility into the DOM state. Severity is low because misuse would at worst leak non-sensitive page structure information to an agent.

From the tool's definition Tool description states it 'Search[es] for DOM elements' and 'Returns matching elements with their paths' — purely a query/retrieval operation with no modification or execution of browser actions.

Documented attack patterns abuse exactly the kind of access search_dom_elements gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ZMCPTools, and nothing reaches the server without passing your rules. This is the rule we recommend for search_dom_elements:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_dom_elements": {}
  }
}

search_dom_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ZMCPTools — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_dom_elements tool do? +

Search for DOM elements by type, content, keywords, or attributes. Returns matching elements with their paths for further navigation. It is categorised as a Read tool in the ZMCPTools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_dom_elements? +

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

What risk level is search_dom_elements? +

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

Can I rate-limit search_dom_elements? +

Yes. Add a rate_limit block to the search_dom_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_dom_elements completely? +

Set action: deny in the PolicyLayer policy for search_dom_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_dom_elements? +

search_dom_elements is provided by the ZMCPTools MCP server (zachhandley/zmcptools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ZMCPTools tool call.

Deterministic rules across all 70 ZMCPTools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

70 ZMCPTools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.