Pause playback on the user
AI agents invoke spotify_pause to trigger actions in Spotify MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool controls Spotify playback by pausing it, which is an external operation with side effects on the user's active session. It doesn't read data, write/modify stored data, delete anything, or involve finances. It falls under Execute as it triggers a media control action on an external service.
From the tool's definition 'Pause playback on the user' — triggers an external operation affecting Spotify playback state
Attacks that exploit this kind of access
Pause playback on the user. It is categorised as a Execute tool in the Spotify MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for spotify_pause: 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_pause is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the spotify_pause 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_pause. 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_pause is provided by the Spotify MCP Server MCP server (llmtooling/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 →