# analyze_page

A read tool on the UI Analyzer MCP Server MCP server.

Agent View of the PolicyLayer registry record for `analyze_page`. HTML page: https://policylayer.com/tools/0x-professor-uianalyzermcp/analyze-page

## Facts

- Tool: `analyze_page`
- Server: UI Analyzer MCP Server (`0x-professor/uianalyzermcp`) — https://policylayer.com/tools/0x-professor-uianalyzermcp.md
- Homepage: https://github.com/0x-Professor/UIAnalyzerMCP
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "analyze_page",
    "arguments": {}
  }
}
```

## Why analyze_page is rated Low

The tool operates within an analysis and instrumentation context focused on examining website properties, not modifying them. Even though it uses Playwright (a browser automation tool capable of executing actions), the server's purpose and all sibling tools indicate read-only, observational use cases. There is no evidence of data modification, deletion, code execution, or financial transactions.

From the tool's own definition: "Tool is part of a UI Analyzer server that uses Playwright to analyze website UIs and provide CSS/HTML instructions."

## Use case

AI agents call analyze_page to retrieve information from UI Analyzer MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches UI Analyzer MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_page": {}
  }
}
```

## Other tools on UI Analyzer MCP Server (7)

- `compare_viewports` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/compare-viewports.md
- `get_accessibility_snapshot` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-accessibility-snapshot.md
- `get_dom_overview` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-dom-overview.md
- `get_element_details` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-element-details.md
- `get_fix_instructions` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-fix-instructions.md
- `get_screenshot` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-screenshot.md
- `get_tech_stack` — Read — https://policylayer.com/tools/0x-professor-uianalyzermcp/get-tech-stack.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=0x-professor-uianalyzermcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0x-professor-uianalyzermcp