Get information about the currently playing track.
AI agents call spotify_current_track 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 retrieves metadata about the currently playing track without modifying any data, triggering playback changes, or affecting user library state. It is a straightforward read operation. Severity is low because misuse (e.g., spamming requests) has minimal impact; the worst outcome is redundant API calls.
From the tool's definition Tool description states 'Get information about the currently playing track' — a retrieval operation with no side effects. Sibling tools include play/pause/like actions, but this tool itself only queries current state.
Attacks that exploit this kind of access
Get information about the currently playing track. 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 spotify_current_track: 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.
spotify_current_track 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 spotify_current_track 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 spotify_current_track. 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.
spotify_current_track is provided by the Spotify MCP Server MCP server (mfteloglu/spotify-mcp-server). 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 →