// SCAN REPORT

Recall

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

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

Last updated: 29 Jun 2026

0 can modify or destroy data

5 read-only

5 tools total

Community server · catalogue entry verified 29/06/2026

How to control Recall ↓

TOOL MAP

What Recall 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 Recall

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

Cap read operations

{
  "get_transcript": {
    "limits": [
      {
        "counter": "get_transcript_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 Recall — 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 RECALL →

Instant setup, no code required.

FULL CATALOGUE

All 5 Recall tools

READ 5 tools

Read get_transcript Fetch the full transcript of a Granola meeting. Supports title + date search (e.g., Read index_granola_transcripts Index Granola meeting transcripts for semantic search. By default additive - only indexes new meetings. Use cl Read index_status Check the current status of the document index, including breakdown by source type. Read reindex_docs Rebuild the vector index for strategy documents. Only affects strategy docs, preserves any indexed transcripts Read semantic_search Search strategy docs and Granola meeting transcripts by meaning, not just keywords. Finds relevant content bas

FAQ

Questions about Recall

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

The Recall 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 Recall 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 Recall? +

Register the Recall 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 Recall tool call.

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

ENFORCE POLICY ON RECALL →

Instant setup, no code required.

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