Render a URL at multiple breakpoints and flag content elements that are visible on desktop but hidden on mobile (display:none / opacity:0 / visibility:hidden / zero-size). Categorises each flag as 'likely-oversight' (content that vanishes on mobile — the hidden-on-mobile content bug) vs 'intentio...
AI agents call audit_responsive_visibility to retrieve information from Raven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | URL to render (http/https or file://) |
breakpoints | array | — | Viewport widths in px. Default [390, 768, 1440, 2160] |
viewportHeight | number | — | Render height in px. Default 900 |
Parameters from the server's own tool schema.
This is a design audit tool that inspects responsive visibility across breakpoints and reports findings. It does not modify, delete, execute, or execute code on the target system—it only analyzes and reports on CSS display properties. The operation is entirely side-effect-free and informational, fitting the 'Read' category.
From the tool's definition Tool 'renders a URL at multiple breakpoints and flag[s] content elements' — performs inspection and analysis only. Returns 'a table of selector / hiding-class / mobile-visible / desktop-visible / category' with no modification of the audited target.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Render a URL at multiple breakpoints and flag content elements that are visible on desktop but hidden on mobile (display:none / opacity:0 / visibility:hidden / zero-size). Categorises each flag as 'likely-oversight' (content that vanishes on mobile — the hidden-on-mobile content bug) vs 'intentional' (decorative). Returns a table of selector / hiding-class / mobile-visible / desktop-visible / category. Requires headless chromium. It is categorised as a Read tool in the Raven MCP Server, which means it retrieves data without modifying state.
audit_responsive_visibility accepts 3 parameters: url, breakpoints, viewportHeight. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Raven MCP server in PolicyLayer and add a rule for audit_responsive_visibility: 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 Raven. Nothing to install.
audit_responsive_visibility 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 audit_responsive_visibility 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 audit_responsive_visibility. 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.
audit_responsive_visibility is provided by the Raven MCP server (raven-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →