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 first to discover available commit IDs.
This record as markdown: /tools/0x1f320-why-did-you-render-mcp/get-renders-by-commit.md
What get_renders_by_commit does on Why Did You Render
AI agents call get_renders_by_commit 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.
Why get_renders_by_commit is rated Low
This tool retrieves performance diagnostic data from a React renderer tracking system. It queries and returns re-render information without side effects. While the data could theoretically inform performance optimizations, the tool itself only reads and returns existing performance metrics. No data is created, modified, deleted, or executed.
From the tool's definition Tool description explicitly states it 'Returns' re-render data and includes the verb 'get_' in the tool name.
Attacks that exploit this kind of access
The rule that runs get_renders_by_commit 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 get_renders_by_commit, this is the rule to start with:
get_renders_by_commit is read-only, so it stays allowed. 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 get_renders_by_commit call is checked against it from then on.
Questions about 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 first to discover available commit IDs. It is categorised as a Read tool in the Why Did You Render MCP Server, which means it retrieves data without modifying state.
Register the Why Did You Render MCP server in PolicyLayer and add a rule for get_renders_by_commit: 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.
get_renders_by_commit is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_renders_by_commit 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 get_renders_by_commit. 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.
get_renders_by_commit 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.
This server
Across the catalogue