Remove tracks or episodes from a playlist. Auto-chunks at 100 items per request.
AI agents call remove_playlist_items to permanently remove resources in Spotify MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing items from a playlist is a destructive operation because it permanently deletes those tracks/episodes from the playlist. While the tracks themselves still exist on Spotify, their removal from the playlist is not automatically reversible (no undo mechanism).
From the tool's definition 'Remove tracks or episodes from a playlist' — explicitly removes items from a playlist, which is a destructive modification that deletes content from the playlist.
Attacks that exploit this kind of access
Remove tracks or episodes from a playlist. Auto-chunks at 100 items per request. It is categorised as a Destructive tool in the Spotify MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for remove_playlist_items: 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 MCP Server. Nothing to install.
remove_playlist_items 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 remove_playlist_items 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 remove_playlist_items. 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.
remove_playlist_items is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →