snapshot_new_tracks

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/snapshot-new-tracks.md

WHAT IT DOES

What snapshot_new_tracks does on Spotify

AI agents call snapshot_new_tracks 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 snapshot_new_tracks is rated Low

Compares playlist snapshots to list new tracks; no modifications or deletions occur.

From the tool's definition List only the tracks added between snapshots, diff operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

snapshot_new_tracks Allowed

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

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 snapshot_new_tracks call is checked against it from then on.

FAQ

Questions about snapshot_new_tracks

What does the snapshot_new_tracks tool do? +

List only the tracks added between an older and a newer snapshot of a 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 snapshot_new_tracks? +

Register the Spotify MCP server in PolicyLayer and add a rule for snapshot_new_tracks: 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 snapshot_new_tracks? +

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

Can I rate-limit snapshot_new_tracks? +

Yes. Add a rate_limit block to the snapshot_new_tracks 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 snapshot_new_tracks completely? +

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

snapshot_new_tracks 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

The MCP Attack Database →

Guides

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