compare_snapshots

Compares two saved render snapshots and shows per-component render count changes.

SERVERWhy Did You Render SOURCE0x1f320/why-did-you-render-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0x1f320-why-did-you-render-mcp/compare-snapshots.md

WHAT IT DOES

What compare_snapshots does on Why Did You Render

AI agents call compare_snapshots 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.

RISK

Why compare_snapshots is rated Low

This tool retrieves and analyzes existing snapshot data to display comparative metrics. It is purely observational with no side effects—it reads performance data and presents differences between two snapshots. No data is modified, deleted, or executed. This is a diagnostic/reporting function characteristic of Read category tools.

From the tool's definition Tool name and description indicate data retrieval and comparison: 'compares two saved render snapshots and shows per-component render count changes.' No creation, modification, deletion, or execution of external operations occurs.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs compare_snapshots 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 compare_snapshots, this is the rule to start with:

compare_snapshots Allowed

compare_snapshots is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_snapshots": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Why Did You Render, apply this rule, and every compare_snapshots call is checked against it from then on.

FAQ

Questions about compare_snapshots

What does the compare_snapshots tool do? +

Compares two saved render snapshots and shows per-component render count changes. It is categorised as a Read tool in the Why Did You Render MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on compare_snapshots? +

Register the Why Did You Render MCP server in PolicyLayer and add a rule for compare_snapshots: 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.

What risk level is compare_snapshots? +

compare_snapshots is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit compare_snapshots? +

Yes. Add a rate_limit block to the compare_snapshots 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.

How do I block compare_snapshots completely? +

Set action: deny in the PolicyLayer policy for compare_snapshots. 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.

What MCP server provides compare_snapshots? +

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

KEEP EXPLORING

More on Why Did You Render, and thousands of servers like it.

This server

All 14 Why Did You Render tools →

Across the catalogue

compare_images on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →