Add the current or specified track to your Liked Songs
AI agents use like_track to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.
This tool creates or modifies user data (liked songs playlist) reversibly. A user can unlike a track if needed, making it a Write operation rather than Destructive. The blast radius is minimal—misuse would only add unwanted tracks to the user's liked songs, which is easily correctable. No financial, destructive, or execute-level impact.
From the tool's definition Tool name 'like_track' and description 'Add the current or specified track to your Liked Songs' indicate a create/modify operation that adds a track to a user's collection.
Attacks that exploit this kind of access
Add the current or specified track to your Liked Songs. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for like_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.
like_track 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 like_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 like_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.
like_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 →