Get the current user's saved tracks.
AI agents call get_saved_tracks 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 queries and returns the user's saved tracks library without creating, modifying, deleting, or executing any operations. It is a straightforward read operation on user data, presenting minimal risk as it only retrieves information the authenticated user already has access to.
From the tool's definition Tool name 'get_saved_tracks' and description 'Get the current user's saved tracks' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get the current user's saved tracks. 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_saved_tracks: 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_saved_tracks 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_saved_tracks 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_saved_tracks. 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_saved_tracks is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). 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 →