spotify_liked_songs
AI agents call spotify_liked_songs to retrieve information from Spotify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'spotify_liked_songs' indicates fetching or listing the user's saved/liked songs from Spotify. This is consistent with other read-only tools in the server (get_info, recently_played, search). No description is provided, which lowers confidence slightly, but the naming convention and server context indicate this is a data retrieval operation with no destructive or modifying capability.
From the tool's definition Tool named 'spotify_liked_songs' with empty description. Based on context (sibling tools include read-only operations like 'spotify_get_info', 'spotify_recently_played', 'spotify_search'), this tool likely retrieves the user's liked/saved songs list.
Documented attack patterns abuse exactly the kind of access spotify_liked_songs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Spotify, and nothing reaches the server without passing your rules. This is the rule we recommend for spotify_liked_songs:
{
"version": "1",
"default": "deny",
"tools": {
"spotify_liked_songs": {}
}
}spotify_liked_songs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
spotify_liked_songs. It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP server in PolicyLayer and add a rule for spotify_liked_songs: 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.
spotify_liked_songs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the spotify_liked_songs 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 spotify_liked_songs. 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.
spotify_liked_songs is provided by the Spotify MCP server (veridyia/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Spotify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Spotify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.