Unfollow (remove) a Spotify playlist from your library.
AI agents call unfollow_playlist to permanently remove resources in Mcp Spotify — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unfollowing/removing a playlist from the user's library is a reversible action in principle (you could re-follow), but it is functionally destructive as it removes the playlist from the library without a built-in undo mechanism within the tool. It most closely matches the Destructive category since the action cannot be undone programmatically by this tool.
From the tool's definition Unfollow (remove) a Spotify playlist from your library
Attacks that exploit this kind of access
Unfollow (remove) a Spotify playlist from your library. It is categorised as a Destructive tool in the Mcp Spotify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Spotify MCP server in PolicyLayer and add a rule for unfollow_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.
unfollow_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 unfollow_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 unfollow_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.
unfollow_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 →