# Why Did You Render MCP server Agent View of the PolicyLayer registry record for Why Did You Render: identity, probed posture, risk grade, and all 14 tools classified. HTML page: https://policylayer.com/tools/0x1f320-why-did-you-render-mcp ## Facts - Server id: `0x1f320/why-did-you-render-mcp` - Homepage: https://github.com/0x1f320/why-did-you-render-mcp - Registry record: grade F, identity unverified - Lifecycle: active - Rate-limited: no - Tools: 14 - Tool categories present: Destructive, Execute, Read, Write - Tags: 0x1f320 why did you render mcp, admin, automation - Record last modified: 2026-06-30T09:53:33.796Z ## Tools (14) | Tool | Category | Risk | Record | | --- | --- | --- | --- | | `clear_renders` | Destructive | Critical | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/clear-renders.md | | `delete_snapshot` | Destructive | Critical | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/delete-snapshot.md | | `pause_renders` | Execute | High | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/pause-renders.md | | `wait_for_renders` | Execute | High | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/wait-for-renders.md | | `compare_snapshots` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/compare-snapshots.md | | `get_commits` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-commits.md | | `get_projects` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-projects.md | | `get_render_summary` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-render-summary.md | | `get_renders` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-renders.md | | `get_renders_by_commit` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-renders-by-commit.md | | `get_tracked_components` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-tracked-components.md | | `list_snapshots` | Read | Low | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/list-snapshots.md | | `resume_renders` | Write | Medium | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/resume-renders.md | | `save_snapshot` | Write | Medium | https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/save-snapshot.md | ## Tool descriptions - `clear_renders` — Clears collected render data. Supports filtering by component name or by commit ID threshold. When no filter is given, clears all data. If multiple projects are active and no project is specified, the tool will ask you to disambiguate. - `delete_snapshot` — Deletes a saved render snapshot by name. - `pause_renders` — Pauses render data collection in the browser. Connected clients will stop reporting renders until resume_renders is called. Useful when you want to ignore renders from irrelevant interactions. If multiple projects are active and no proje… - `wait_for_renders` — Waits for new renders to arrive after a code change. Call this after modifying code to wait for HMR to complete and measure the resulting re-renders. Returns a summary of new renders received during the wait period. - `compare_snapshots` — Compares two saved render snapshots and shows per-component render count changes. - `get_commits` — Returns a list of React commit IDs that have recorded render data for a project. Use these IDs with get_renders_by_commit to inspect individual commits. - `get_projects` — Returns a list of project identifiers (browser origin URLs) that have recorded render data. - `get_render_summary` — Returns a summary of re-renders grouped by component name with counts. Use groupBy: - `get_renders` — Returns all re-renders collected from the browser, including stack traces that show the hook chain and component tree that triggered each render. Use the stackFrames field to locate the exact source file and line. If multiple projects ar… - `get_renders_by_commit` — Returns all re-renders for a specific React commit ID, including stack traces that show the hook chain and component tree that triggered each render. Use the stackFrames field to locate the exact source file and line. Use get_commits fir… - `get_tracked_components` — Returns the why-did-you-render configuration for the connected project, including include/exclude filters and tracking options. Also shows components observed in render data. If multiple projects are active and no project is specified, t… - `list_snapshots` — Lists all saved render snapshots with their timestamps. - `resume_renders` — Resumes render data collection that was previously paused with pause_renders. Connected clients will start reporting renders again. If multiple projects are active and no project is specified, the tool will ask you to disambiguate. - `save_snapshot` — Saves the current render summary as a named snapshot for later comparison. If multiple projects are active and no project is specified, the tool will ask you to disambiguate. ## Related servers - UnClick (1658 tools) — https://policylayer.com/tools/io-github-malamutemayhem-unclick-mcp-server.md - Nodebench (824 tools) — https://policylayer.com/tools/io-github-homenshum-nodebench.md - Yaver (805 tools) — https://policylayer.com/tools/io-github-kivanccakmak-yaver.md - Binance MCP Server (734 tools) — https://policylayer.com/tools/nirholas-binance-mcp.md - Fortimanager (584 tools) — https://policylayer.com/tools/jmpijll-fortimanager-mcp.md - Crow (578 tools) — https://policylayer.com/tools/kh0pper-crow.md - TinyFn (572 tools) — https://policylayer.com/tools/io-tinyfn-tinyfn.md - Mcp (571 tools) — https://policylayer.com/tools/io-github-2s-io-mcp.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=0x1f320-why-did-you-render-mcp · API: https://policylayer.com/registry/api · Recommended policies for every tool: https://policylayer.com/policies/0x1f320-why-did-you-render-mcp