// SCAN REPORT

Mcp Browser Lens

31 tools. 1 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

1 can modify or destroy data

30 read-only

31 tools total

Community server · catalogue entry verified 29/06/2026

How to control Mcp Browser Lens ↓

TOOL MAP

What Mcp Browser Lens exposes to your agents

Read (30) Write / Execute (0) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Mcp Browser Lens tools

Destructive · High clear_data This tool permanently deletes all stored browser analysis data (DOM snapshots, styles, screenshots, and comparison history).

1 of Mcp Browser Lens's 31 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Mcp Browser Lens

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Browser Lens, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_data": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "capture_screenshot_with_analysis": {
    "limits": [
      {
        "counter": "capture_screenshot_with_analysis_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Mcp Browser Lens — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP BROWSER LENS →

Instant setup, no code required.

FULL CATALOGUE

All 31 Mcp Browser Lens tools

DESTRUCTIVE 1 tools

Destructive clear_data Clear all captured browser data: DOM, styles, screenshots, comparisons

READ 30 tools

Read capture_screenshot_with_analysis Get the latest screenshot AND a detailed analysis of what Read compare_with_figma Compare a browser element against Figma design specifications. Provide the expected CSS values from Figma and Read describe_ui Generate a comprehensive AI-friendly description of the current page layout, colors, typography, and interacti Read get_accessibility_info Check interactive elements for ARIA labels, roles, alt text, headings, and landmarks Read get_all_screenshots List all captured screenshots with metadata Read get_color_palette Extract all colors (text, background, border) used on the page with usage counts Read get_comparison_history Get all previous Figma comparison results Read get_computed_styles Get all computed CSS styles for a specific element including applied classes and matched rules Read get_connection_status Check if the browser is connected and what data is available. Use this first to verify the bookmarklet is acti Read get_css_variables Get all CSS custom properties (--) defined in the page with their values Read get_design_tokens Extract design tokens from the page: CSS variables grouped by category (colors, typography, spacing, breakpoin Read get_dom_mutations Get recent DOM changes (attribute changes, added/removed nodes) Read get_dom_tree Get the full DOM tree structure of the connected page with semantic analysis Read get_element_hierarchy Show parent-child relationships for a specific element in the DOM tree Read get_elements_summary Get a summary of all captured element details with their selectors Read get_full_page_analysis Get a comprehensive analysis of the entire page: structure, design tokens, typography, colors, spacing, access Read get_layout_info Get box model, positioning, flex/grid info, and dimensions for an element Read get_page_info Get connected page URL, viewport size, element count, and data availability summary Read get_page_screenshot Get the latest screenshot of the page viewport as a PNG image Read get_responsive_info Get viewport dimensions, device pixel ratio, active media queries, and breakpoint status Read get_spacing_analysis Analyze margins, paddings, and gaps across elements to find inconsistencies and spacing scale Read get_typography Analyze all font families, sizes, weights, and line-heights used on the page Read get_visual_diff_report Generate a comprehensive visual diff report comparing the current UI against all previously compared Figma spe Read inspect_element Get full details of a specific element: DOM, computed styles, layout, box model, accessibility Read inspect_feature_area Inspect a specific feature area of the page by providing a parent selector. Returns screenshot + all child ele Read live_query_element Query the browser in real-time to inspect ANY element by CSS selector — even deeply nested ones. Sends a comma Read query_selector Search the DOM tree for elements matching a tag name, class, or ID Read screenshot_element Take a screenshot of a specific UI component/element by CSS selector. Returns the cropped PNG image of just th Read suggest_css_fixes Based on the latest Figma comparison, suggest specific CSS changes to match the design Read trigger_screenshot Take a screenshot of the current browser page. Uses Chrome DevTools Protocol for reliable capture (requires Ch

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Mcp Browser Lens

Can an AI agent delete data through the Mcp Browser Lens MCP server? +

Yes. The Mcp Browser Lens server exposes 1 destructive tools including clear_data. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Mcp Browser Lens MCP server expose? +

31 tools across 3 categories: Destructive, Execute, Read. 30 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Mcp Browser Lens? +

Register the Mcp Browser Lens MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Mcp Browser Lens tool call.

Deterministic rules across all 31 Mcp Browser Lens tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP BROWSER LENS →

Instant setup, no code required.

31 Mcp Browser Lens tools catalogued and risk-classified — across an index of 43,000+ MCP servers.