describe_element
Get detailed information about a DOM element. Args: node_id: Node ID of the element depth: Depth of child nodes to include Returns: Detailed element description including tag, attributes, and children
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/describe-element.md
What describe_element does on Chrome Devtools
AI agents call describe_element 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 describe_element is rated Low
This is a retrieval operation with no side effects. It queries and returns information about the DOM structure without modifying, executing code, or affecting any state. The return value is purely informational data about element properties and children. This fits the 'Read' category as a query/get operation.
From the tool's definition The tool 'describe_element' retrieves detailed information about a DOM element by querying node properties, attributes, and hierarchy.
Attacks that exploit this kind of access
The rule that runs describe_element 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 describe_element, this is the rule to start with:
describe_element 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 describe_element call is checked against it from then on.
Questions about describe_element
Get detailed information about a DOM element. Args: node_id: Node ID of the element depth: Depth of child nodes to include Returns: Detailed element description including tag, attributes, and children. 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 describe_element: 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.
describe_element 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 describe_element 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 describe_element. 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.
describe_element 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