Get track recommendations based on seed tracks, artists, or genres. Can automatically use recent listening history if no seeds provided.
AI agents call get_recommendations to retrieve information from Spotify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves recommendation data based on seed inputs or listening history. It does not create, modify, delete, or execute any operations with side effects. The blast radius of misuse is minimal—at worst, an agent requesting irrelevant recommendations wastes API quota but causes no harm to the user's account, playlists, or playback state.
From the tool's definition Tool is described as 'Get track recommendations' which retrieves data from Spotify's recommendation engine.
Attacks that exploit this kind of access
Get track recommendations based on seed tracks, artists, or genres. Can automatically use recent listening history if no seeds provided. It is categorised as a Read tool in the Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for get_recommendations: 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.
get_recommendations 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 get_recommendations 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 get_recommendations. 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.
get_recommendations is provided by the Spotify MCP Server MCP server (nicklaustrup/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 →