delete_playlist_snapshot

Delete one local playlist snapshot file; dry_run=true (default) only reports what would be removed

SERVERSpotify SOURCE@novalux12/spotify-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/delete-playlist-snapshot.md

WHAT IT DOES

What delete_playlist_snapshot does on Spotify

AI agents call delete_playlist_snapshot to permanently remove resources in Spotify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_playlist_snapshot is rated Critical

An AI agent that decides to call delete_playlist_snapshot doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Spotify is gone. There is no undo for destructive operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

delete_playlist_snapshot Hidden

delete_playlist_snapshot is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_playlist_snapshot"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_playlist_snapshot

What does the delete_playlist_snapshot tool do? +

Delete one local playlist snapshot file; dry_run=true (default) only reports what would be removed. It is categorised as a Destructive tool in the Spotify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_playlist_snapshot? +

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

delete_playlist_snapshot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_playlist_snapshot? +

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

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

delete_playlist_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 544 Spotify tools → Critical-risk tools on this server →

Across the catalogue

delete_snapshot on Why Did You Render →sms_delete_message on Twilio SMS MCP Server →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →