// SCAN REPORT

Rewind

5 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 30 Jun 2026

0 can modify or destroy data

5 read-only

5 tools total

Community server · catalogue entry verified 30/06/2026

How to control Rewind ↓

TOOL MAP

What Rewind exposes to your agents

Read (5) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Rewind

PolicyLayer is an MCP gateway — it sits between your AI agents and Rewind, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "diff_snapshots": {
    "limits": [
      {
        "counter": "diff_snapshots_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rewind — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REWIND →

Instant setup, no code required.

FULL CATALOGUE

All 5 Rewind tools

READ 5 tools

Read diff_snapshots Compares two snapshots (or the latest snapshot vs current state) to show what changed between them. Useful for Read get_context_status Shows the current status of the Rewind agent: tracked directories, snapshot counts, and storage info. Useful f Read recent_activity Shows a timeline of recent development activity in a project directory. Combines git commits, file modificatio Read take_snapshot Takes a point-in-time snapshot of your current working context. Captures git state, recently modified files, e Read where_was_i Reconstructs your working context after an interruption. Analyzes git state (branch, uncommitted changes, rece

FAQ

Questions about Rewind

Is the Rewind MCP server safe to use without restrictions? +

The Rewind server is primarily read-only with 5 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Rewind MCP server expose? +

5 tools across 1 categories: Read. 5 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Rewind? +

Register the Rewind MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rewind tool call.

Deterministic rules across all 5 Rewind tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REWIND →

Instant setup, no code required.

5 Rewind tools catalogued and risk-classified — across an index of 43,000+ MCP servers.