Remove the current or specified track from your Liked Songs
AI agents call unlike_track to permanently remove resources in Spotify MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unliking a track removes it from the user's Liked Songs library. While not permanently deleting data (the track still exists on Spotify), this action reverses a saved preference and could be difficult to undo at scale if an AI agent misuses it across many tracks. The removal is effectively irreversible without knowing which tracks were affected, placing it closer to Destructive than Write.
From the tool's definition Remove the current or specified track from your Liked Songs
Attacks that exploit this kind of access
Remove the current or specified track from your Liked Songs. It is categorised as a Destructive tool in the Spotify MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for unlike_track: 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 MCP Server. Nothing to install.
unlike_track 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 unlike_track 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 unlike_track. 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.
unlike_track is provided by the Spotify MCP Server MCP server (madhurtoshniwal/spotify-mcp-server). 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 →