find_lost_since_snapshot

SERVERSpotify SOURCE@novalux12/spotify-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/novalux12-spotify-mcp/find-lost-since-snapshot.md

WHAT IT DOES

What find_lost_since_snapshot does on Spotify

AI agents call find_lost_since_snapshot to retrieve information from Spotify without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why find_lost_since_snapshot is rated Low

Tool queries and compares playlist data without modifying or executing external operations.

From the tool's definition Compare a live playlist against a snapshot and list snapshot tracks that have since disappeared

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs find_lost_since_snapshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For find_lost_since_snapshot, this is the rule to start with:

find_lost_since_snapshot Allowed

find_lost_since_snapshot 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": {
    "find_lost_since_snapshot": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every find_lost_since_snapshot call is checked against it from then on.

FAQ

Questions about find_lost_since_snapshot

What does the find_lost_since_snapshot tool do? +

Compare a live playlist against a snapshot and list snapshot tracks that have since disappeared from the playlist Snapshot guide: take_playlist_snapshot (create), list_saved_snapshots (list), read_playlist_snapshot (read), diff_playlist_snapshots / snapshot_new_tracks / snapshot_removed_tracks (diff), restore_playlist_from_snapshot / restore_playlist_plan (restore). It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on find_lost_since_snapshot? +

Register the Spotify MCP server in PolicyLayer and add a rule for find_lost_since_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 Spotify. Nothing to install.

What risk level is find_lost_since_snapshot? +

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

Can I rate-limit find_lost_since_snapshot? +

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

How do I block find_lost_since_snapshot completely? +

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

What MCP server provides find_lost_since_snapshot? +

find_lost_since_snapshot is provided by the Spotify MCP server (@novalux12/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools →

Across the catalogue

find_callees on ACE-MCP → The MCP Attack Database →

Guides

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