# 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 are active and no project is specified, the tool will ask you to disambiguate by asking the user for their dev server URL.

Agent View of the PolicyLayer registry record for `get_renders`. HTML page: https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-renders

## Facts

- Tool: `get_renders`
- Server: Why Did You Render (`0x1f320/why-did-you-render-mcp`) — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp.md
- Homepage: https://github.com/0x1f320/why-did-you-render-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, 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": "get_renders",
    "arguments": {}
  }
}
```

## Why get_renders is rated Low

The tool retrieves and queries performance diagnostic data (re-render traces and stack frames) from a React development environment. It has no side effects, does not modify state, execute code, or trigger external operations. The data returned is read-only diagnostic information useful for performance analysis.

From the tool's own definition: "Tool description states it 'Returns all re-renders collected from the browser' and uses 'get_' naming convention, indicating data retrieval. No modification, deletion, or execution capabilities are described."

## Use case

AI agents call get_renders to retrieve information from Why Did You Render 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 Why Did You Render:

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

## Other tools on Why Did You Render (13)

- `clear_renders` — Destructive — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/clear-renders.md
- `delete_snapshot` — Destructive — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/delete-snapshot.md
- `pause_renders` — Execute — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/pause-renders.md
- `wait_for_renders` — Execute — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/wait-for-renders.md
- `compare_snapshots` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/compare-snapshots.md
- `get_commits` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-commits.md
- `get_projects` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-projects.md
- `get_render_summary` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-render-summary.md
- `get_renders_by_commit` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-renders-by-commit.md
- `get_tracked_components` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-tracked-components.md
- `list_snapshots` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/list-snapshots.md
- `resume_renders` — Write — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/resume-renders.md
- `save_snapshot` — Write — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/save-snapshot.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 · Policy library: https://policylayer.com/policies/0x1f320-why-did-you-render-mcp