Get a list of your Spotify playlists. Returns playlist names, IDs, track counts, and whether they
AI agents call get_user_playlists to retrieve information from Your 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 retrieves and queries playlist metadata without altering any data. It has no side effects and causes no irreversible changes. The blast radius of misuse is minimal (information disclosure only), making it a straightforward Read category with low severity.
From the tool's definition Tool description states 'Get a list of your Spotify playlists' and 'Returns playlist names, IDs, track counts' — purely informational retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get a list of your Spotify playlists. Returns playlist names, IDs, track counts, and whether they. It is categorised as a Read tool in the Your Spotify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Your Spotify MCP Server MCP server in PolicyLayer and add a rule for get_user_playlists: 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 Your Spotify MCP Server. Nothing to install.
get_user_playlists 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_user_playlists 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_user_playlists. 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_user_playlists is provided by the Your Spotify MCP Server MCP server (pentafive/your-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 →