AI agents call spotify_current_playback to retrieve information from Spotify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and returns information about the current playback status without creating, modifying, deleting, or executing any actions. It has no side effects and poses minimal security risk. The low severity reflects that playback state information is non-sensitive metadata that does not require any protective measures.
From the tool's definition Tool retrieves current playback state (track, device, position, etc.) with no modification of data or triggering of actions. The verb 'Get' and the fact it returns state information confirms this is a read-only query operation.
Attacks that exploit this kind of access
Get current playback state (track, device, position, etc.). It is categorised as a Read tool in the Spotify MCP Server, which means it retrieves data without modifying state.
Register the Spotify MCP server in PolicyLayer and add a rule for spotify_current_playback: 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. Nothing to install.
spotify_current_playback 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_playback 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_playback. 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_playback is provided by the Spotify MCP server (thebigredgeek/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 →