get_matched_styles
Get comprehensive style information including all CSS rules matching a DOM element. Args: node_id: Node ID of the element Returns: Complete style analysis including cascade, inheritance, and pseudo-elements
This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-matched-styles.md
What get_matched_styles does on Chrome Devtools
AI agents call get_matched_styles 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_matched_styles is rated Low
This tool retrieves CSS style information for a DOM element. It queries and returns data about matching CSS rules, cascade properties, and inheritance—all read-only operations with no side effects. While it operates in a browser context via Chrome DevTools Protocol, it does not execute code, modify state, delete data, or trigger external operations.
From the tool's definition Tool name is 'get_matched_styles' and description states it 'Get comprehensive style information' and 'Returns: Complete style analysis'.
Attacks that exploit this kind of access
The rule that runs get_matched_styles 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_matched_styles, this is the rule to start with:
get_matched_styles 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_matched_styles call is checked against it from then on.
Questions about get_matched_styles
Get comprehensive style information including all CSS rules matching a DOM element. Args: node_id: Node ID of the element Returns: Complete style analysis including cascade, inheritance, and pseudo-elements. 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_matched_styles: 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_matched_styles 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_matched_styles 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_matched_styles. 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_matched_styles 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