get_element_attributes
Get all attributes of a DOM element. Args: node_id: Node ID of the element Returns: Dictionary of element attributes
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-element-attributes.md
What get_element_attributes does on Chrome Devtools
AI agents call get_element_attributes 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_attributes is rated Low
This tool retrieves information about a DOM element's attributes without creating, modifying, deleting, or executing anything. It has no side effects—it simply queries and returns existing data. The blast radius of misuse is minimal since an attacker can only read attribute values visible in the DOM, not alter browser state or execute code.
From the tool's definition Tool description states it "Get[s] all attributes of a DOM element" and "Returns: Dictionary of element attributes". The verb 'get' and lack of any modification operation indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs get_element_attributes 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_attributes, this is the rule to start with:
get_element_attributes 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_attributes call is checked against it from then on.
Questions about get_element_attributes
Get all attributes of a DOM element. Args: node_id: Node ID of the element Returns: Dictionary of element attributes. 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_attributes: 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_attributes 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_attributes 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_attributes. 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_attributes 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