Follow (save) a Spotify playlist to your library.
AI agents use follow_playlist to create or update resources in Mcp Spotify — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Spotify environment.
This tool modifies the user's saved playlists collection by adding an entry, which is a reversible write operation. It is not destructive (can be unfollowed), not financial, and not execute (no code/shell invocation). The severity is medium because bulk misuse could clutter a user's library and modify their Spotify account state, but the effect is limited in scope and easily reversible.
From the tool's definition The tool 'follow_playlist' performs a state-changing action—it saves/adds a playlist to the user's library. This is explicitly a modification operation (follow/save) that creates a new relationship between the user and the playlist resource.
Attacks that exploit this kind of access
Follow (save) a Spotify playlist to your library. It is categorised as a Write tool in the Mcp Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Spotify MCP server in PolicyLayer and add a rule for follow_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 Mcp Spotify. Nothing to install.
follow_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 follow_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 follow_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.
follow_playlist is provided by the Mcp Spotify MCP server (obrien-matthew/mcp-spotify). 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 →