Get detailed listening statistics for a specific track from your listening history. Returns information including: - Total play count across all time - Total listening time - First and last time you played the track - Average plays per day - Your peak listening day for this track Example queries: -
AI agents call get_track_stats 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 historical listening data about a specific track. It has no side effects—it only retrieves pre-existing statistics from the user's listening history. There is no capability to modify playlists, control playback, delete data, or trigger external operations. The blast radius of misuse is minimal, as an AI agent can only read personal listening analytics.
From the tool's definition Tool retrieves 'detailed listening statistics' and 'returns information' about play counts, listening time, and historical data without any stated capability to modify, delete, or execute operations.
Attacks that exploit this kind of access
Get detailed listening statistics for a specific track from your listening history. Returns information including: - Total play count across all time - Total listening time - First and last time you played the track - Average plays per day - Your peak listening day for this track Example queries: -. 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_track_stats: 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_track_stats 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_track_stats 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_track_stats. 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_track_stats 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 →