get_element_outer_html
Get the outer HTML of a DOM element. Args: node_id: Node ID of the element Returns: Outer HTML string of the element
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-element-outer-html.md
What get_element_outer_html does on Chrome Devtools
AI agents call get_element_outer_html 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.
Why get_element_outer_html is rated Low
The tool retrieves DOM element structure as a string. It has no side effects, does not modify state, execute code, or affect external systems. It is a pure read operation on browser DOM state, analogous to inspection/querying tools. The presence of sibling destructive tools (clear_all_cookies, clear_storage) does not change the classification of this specific read-only tool.
From the tool's definition Tool description states 'Get the outer HTML of a DOM element' and 'Returns: Outer HTML string of the element'. This is a retrieval operation that reads and returns DOM data without modification or execution.
Attacks that exploit this kind of access
The rule that runs get_element_outer_html 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 get_element_outer_html, this is the rule to start with:
get_element_outer_html 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 Chrome Devtools, apply this rule, and every get_element_outer_html call is checked against it from then on.
Questions about get_element_outer_html
Get the outer HTML of a DOM element. Args: node_id: Node ID of the element Returns: Outer HTML string of the element. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.
Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_element_outer_html: 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.
get_element_outer_html 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 get_element_outer_html 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 get_element_outer_html. 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.
get_element_outer_html 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.
More on Chrome Devtools, and thousands of servers like it.
This server
Across the catalogue