get_media_queries

Get all media queries parsed by the rendering engine. Returns: List of all active media queries

SERVERChrome Devtools SOURCEbenjaminr/chrome-devtools-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/benjaminr-chrome-devtools-mcp/get-media-queries.md

What get_media_queries does on Chrome Devtools

AI agents call get_media_queries 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_media_queries is rated Low

This tool retrieves and returns information about CSS media queries without modifying any state, executing arbitrary code, or causing side effects. It is a straightforward query operation that reads data from the browser's rendering engine. The low severity reflects minimal risk if misused by an agent — the information returned is passive and already public on the page.

From the tool's definition Tool name is 'get_media_queries' and description states 'Get all media queries parsed by the rendering engine. Returns: List of all active media queries' — indicates a retrieval operation with no modification or execution of code.

Questions about get_media_queries

What does the get_media_queries tool do? +

Get all media queries parsed by the rendering engine. Returns: List of all active media queries. It is categorised as a Read tool in the Chrome Devtools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_media_queries? +

Register the Chrome Devtools MCP server in PolicyLayer and add a rule for get_media_queries: 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.

What risk level is get_media_queries? +

get_media_queries is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_media_queries? +

Yes. Add a rate_limit block to the get_media_queries 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.

How do I block get_media_queries completely? +

Set action: deny in the PolicyLayer policy for get_media_queries. 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.

What MCP server provides get_media_queries? +

get_media_queries 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Chrome Devtools's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.