unfollow_playlist
Unfollow a playlist — remove it from your Spotify library — via DELETE /me/library. Always asks before writing unless SPOTIFY_MCP_CONFIRM=never.
This record as markdown: /tools/novalux12-spotify-mcp/unfollow-playlist.md
What unfollow_playlist does on Spotify
AI agents call unfollow_playlist 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.
Why unfollow_playlist is rated Critical
Removes a playlist from library via DELETE; action is irreversible without re-following.
From the tool's definition Unfollow a playlist — remove it from your Spotify library — via DELETE
Attacks that exploit this kind of access
The rule that runs unfollow_playlist 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 unfollow_playlist, this is the rule to start with:
unfollow_playlist is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every unfollow_playlist call is checked against it from then on.
Questions about unfollow_playlist
Unfollow a playlist — remove it from your Spotify library — via DELETE /me/library. Always asks before writing unless SPOTIFY_MCP_CONFIRM=never. 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.
Register the Spotify MCP server in PolicyLayer and add a rule for unfollow_playlist: 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.
unfollow_playlist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unfollow_playlist 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.
Set action: deny in the PolicyLayer policy for unfollow_playlist. 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.
unfollow_playlist 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.
More on Spotify, and thousands of servers like it.
Across the catalogue