save_snapshot
Saves the current render summary as a named snapshot for later comparison. 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/save-snapshot.md
What save_snapshot does on Why Did You Render
AI agents use save_snapshot 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.
Why save_snapshot is rated Medium
This tool creates and stores snapshots of React render data, which are reversible operations (snapshots can be deleted via the sibling delete_snapshot tool). The write is scoped to diagnostic data collection without side effects on application functionality or data integrity.
From the tool's definition Tool description states 'Saves the current render summary as a named snapshot' which creates and persists new data in the form of named snapshots for later retrieval and comparison.
Attacks that exploit this kind of access
The rule that runs save_snapshot 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 save_snapshot, this is the rule to start with:
save_snapshot stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 save_snapshot call is checked against it from then on.
Questions about save_snapshot
Saves the current render summary as a named snapshot for later comparison. If multiple projects are active and no project is specified, the tool will ask you to disambiguate. It is categorised as a Write tool in the Why Did You Render MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Why Did You Render MCP server in PolicyLayer and add a rule for save_snapshot: 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.
save_snapshot is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_snapshot 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 save_snapshot. 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.
save_snapshot 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