List the current user's Spotify playlists.
AI agents call get_my_playlists to retrieve information from Mcp Spotify 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 user playlist information without side effects. It is a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an agent could enumerate playlists but cannot harm data or finances.
From the tool's definition Tool name 'get_my_playlists' and description 'List the current user's Spotify playlists' indicates retrieval of existing playlist data with no modification or deletion capability.
Attacks that exploit this kind of access
List the current user's Spotify playlists. It is categorised as a Read tool in the Mcp Spotify MCP Server, which means it retrieves data without modifying state.
Register the Mcp Spotify MCP server in PolicyLayer and add a rule for get_my_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 Mcp Spotify. Nothing to install.
get_my_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_my_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_my_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_my_playlists is provided by the Mcp Spotify MCP server (obrien-matthew/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 →