playlist_fill_from_search
Grow a playlist to N items from search queries you supply: round-robin one pick per query per pass, first unseen track match wins, pages each query in Spotify-compliant 10-result requests, then performs chunked adds. Complements listening-data grow_playlist. Quota: one or more 10-result search pa...
This record as markdown: /tools/novalux12-spotify-mcp/playlist-fill-from-search.md
What playlist_fill_from_search does on Spotify
AI agents use playlist_fill_from_search 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 playlist_fill_from_search is rated Medium
Modifies playlists by adding tracks; reversible but affects user's library.
From the tool's definition Grow a playlist, performs chunked adds, modify playlist
Attacks that exploit this kind of access
The rule that runs playlist_fill_from_search 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 playlist_fill_from_search, this is the rule to start with:
playlist_fill_from_search 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 playlist_fill_from_search call is checked against it from then on.
Questions about playlist_fill_from_search
Grow a playlist to N items from search queries you supply: round-robin one pick per query per pass, first unseen track match wins, pages each query in Spotify-compliant 10-result requests, then performs chunked adds. Complements listening-data grow_playlist. Quota: one or more 10-result search pages per query + chunked adds, after a capped pre-read of the current items; a capped pre-read reports existing_truncated and an unknown resulting length. 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 playlist_fill_from_search: 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.
playlist_fill_from_search 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 playlist_fill_from_search 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 playlist_fill_from_search. 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.
playlist_fill_from_search 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