# 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.

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

## Facts

- Tool: `clear_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: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why clear_renders is rated Critical

This tool irreversibly deletes performance monitoring data (render snapshots and metrics). While the data could theoretically be re-collected by re-running the application, the tool itself performs a destructive operation that cannot be undone. The high severity reflects that an agent could accidentally wipe all performance analysis history for a project, losing valuable diagnostic information.

From the tool's own definition: "The tool 'clears collected render data' with no mention of reversibility. The description states 'clears all data' when no filter is given, indicating wholesale deletion of accumulated performance metrics."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call clear_renders to permanently remove resources in Why Did You Render, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Why Did You Render:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "clear_renders"
  ]
}
```

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

- `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` — Read — https://policylayer.com/tools/0x1f320-why-did-you-render-mcp/get-renders.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