Get the current playback state
AI agents call get_playback_state 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 queries the current state of playback (e.g., which track is playing, progress, whether paused/playing). It retrieves information without modifying, creating, deleting, or executing any actions. No financial transactions, code execution, or data destruction occurs. The blast radius of misuse is minimal—an agent could only learn what the user is currently listening to.
From the tool's definition Tool name 'get_playback_state' and description 'Get the current playback state' indicate a retrieval operation with no side effects. The verb 'get' and the read-only nature of querying current state confirm this is a data retrieval action.
Attacks that exploit this kind of access
Get the current playback state. 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 get_playback_state: 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.
get_playback_state 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_playback_state 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_playback_state. 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_playback_state is provided by the Spotify MCP Server MCP server (rakshitha2207/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 →