queue_playlist
Queue all tracks from a playlist/album/artist URI in order (cap 200). mode=append adds to end; mode=replace is not supported — Spotify has no queue-clear endpoint.
This record as markdown: /tools/novalux12-spotify-mcp/queue-playlist.md
What queue_playlist does on Spotify
AI agents call queue_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 queue_playlist is rated Critical
An AI agent that decides to call queue_playlist 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
The rule that runs queue_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 queue_playlist, this is the rule to start with:
queue_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 queue_playlist call is checked against it from then on.
Questions about queue_playlist
Queue all tracks from a playlist/album/artist URI in order (cap 200). mode=append adds to end; mode=replace is not supported — Spotify has no queue-clear endpoint. 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 queue_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.
queue_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 queue_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 queue_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.
queue_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