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

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

## Facts

- Tool: `resume_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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why resume_renders is rated Medium

The tool changes the operational state of render tracking (paused → resumed) but does not create persistent data, delete anything, or execute arbitrary code. This is a state modification that can be reversed by calling pause_renders, making it a Write operation.

From the tool's own definition: "Tool description states it 'Resumes render data collection that was previously paused' — this modifies the state of the data collection system by changing it from paused to active, which is a reversible state change."

## Use case

AI agents use resume_renders to create or update resources in Why Did You Render, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Why Did You Render environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. 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": {
    "resume_renders": {
      "limits": [
        {
          "counter": "resume_renders_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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` — 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
- `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