Find where a specific artist ranks in your listening history. Shows the artist
AI agents call get_artist_rank 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 queries and returns ranking information about an artist within the user's listening history. It has no side effects, does not modify data, execute commands, or trigger external operations beyond data retrieval. It is a simple Read operation with minimal risk.
From the tool's definition Tool name 'get_artist_rank' and description 'Find where a specific artist ranks in your listening history' indicate a query operation that retrieves ranking data without modification.
Attacks that exploit this kind of access
Find where a specific artist ranks in your listening history. Shows the artist. 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_artist_rank: 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_artist_rank 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_artist_rank 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_artist_rank. 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_artist_rank 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 →