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 project is specified, the tool will ask you to disambiguate.
This record as markdown: /tools/0x1f320-why-did-you-render-mcp/pause-renders.md
What pause_renders does on Why Did You Render
AI agents invoke pause_renders to trigger actions in Why Did You Render. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why pause_renders is rated High
This tool triggers an external operation in the browser — stopping active data collection across connected clients. It is not merely reading data, nor does it delete or overwrite anything permanently. It executes a state change in connected browser clients, halting their reporting behavior, which qualifies as Execute.
From the tool's definition Pauses render data collection in the browser. Connected clients will stop reporting renders until resume_renders is called.
Attacks that exploit this kind of access
The rule that runs pause_renders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Why Did You Render, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pause_renders, this is the rule to start with:
pause_renders stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Why Did You Render, apply this rule, and every pause_renders call is checked against it from then on.
Questions about 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 project is specified, the tool will ask you to disambiguate. It is categorised as a Execute tool in the Why Did You Render MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Why Did You Render MCP server in PolicyLayer and add a rule for pause_renders: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Why Did You Render. Nothing to install.
pause_renders is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the pause_renders rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for pause_renders. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
pause_renders is provided by the Why Did You Render MCP server (0x1f320/why-did-you-render-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Why Did You Render, and thousands of servers like it.
Across the catalogue