AI agents call query_dom_elements to retrieve information from Chrome Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
DOM queries retrieve element information from the page structure without modifying state, executing code, or triggering actions. While the empty description reduces confidence slightly, the naming convention and context of other tools on this server clearly indicate a read-only operation. This carries low risk as it only exposes page structure information to the agent.
From the tool's definition Tool name 'query_dom_elements' indicates DOM querying/retrieval. No description provided, but sibling tools like 'execute_script' and 'click_element' suggest this server operates on browser state.
Documented attack patterns abuse exactly the kind of access query_dom_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chrome Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for query_dom_elements:
{
"version": "1",
"default": "deny",
"tools": {
"query_dom_elements": {}
}
}query_dom_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
query_dom_elements. It is categorised as a Read tool in the Chrome Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chrome Tools MCP Server MCP server in PolicyLayer and add a rule for query_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 Chrome Tools MCP Server. Nothing to install.
query_dom_elements 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 query_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.
Set action: deny in the PolicyLayer policy for query_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.
query_dom_elements is provided by the Chrome Tools MCP Server MCP server (nicholmikey/chrome-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 Chrome Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 Chrome Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.