refresh_smart_playlist
Rebuild a playlist from its persisted rule: resolve candidates, then replace the contents (PUT /playlists/{id}/items), creating the playlist on the first refresh. A non-dry-run refresh always writes. The playlist id is stored back on the rule so later refreshes replace it. Every source has a pool...
This record as markdown: /tools/novalux12-spotify-mcp/refresh-smart-playlist.md
What refresh_smart_playlist does on Spotify
AI agents use refresh_smart_playlist to create or update resources in Spotify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify environment.
Why refresh_smart_playlist is rated Medium
Replaces entire playlist contents and can create new playlists; reversible but high blast radius.
From the tool's definition replace the contents (PUT /playlists/{id}/items), creating the playlist
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs refresh_smart_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 refresh_smart_playlist, this is the rule to start with:
refresh_smart_playlist stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every refresh_smart_playlist call is checked against it from then on.
Questions about refresh_smart_playlist
Rebuild a playlist from its persisted rule: resolve candidates, then replace the contents (PUT /playlists/{id}/items), creating the playlist on the first refresh. A non-dry-run refresh always writes. The playlist id is stored back on the rule so later refreshes replace it. Every source has a pool ceiling (top_tracks 100, recently_played 50, saved_tracks scan_cap), reported as pool_capped with pool_cap — a capped pool is a floor, not a complete scan. It is categorised as a Write tool in the Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP server in PolicyLayer and add a rule for refresh_smart_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.
refresh_smart_playlist is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the refresh_smart_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 refresh_smart_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.
refresh_smart_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.
This server
Across the catalogue