spotify_next · Spotify MCP: Risk & Policy

WHAT IT DOES

What spotify_next does on Spotify

AI agents invoke spotify_next to trigger actions in Spotify. 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.

WHY IT NEEDS A POLICY

Why spotify_next needs a policy

This tool triggers an external operation on Spotify's playback system (skipping to the next track). It is not purely reading data, nor does it write/create data or delete anything. It executes a playback control action with minimal blast radius.

From the tool's definition Skip to next track

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_next Rate-limited

spotify_next stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "spotify_next": {
      "limits": [
        {
          "counter": "spotify_next_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Spotify, so you can run agents against it safely.

FAQ

Questions about spotify_next

What does the spotify_next tool do? +

Skip to next track. It is categorised as a Execute tool in the Spotify MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spotify_next? +

Register the Spotify MCP server in PolicyLayer and add a rule for spotify_next: 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.

What risk level is spotify_next? +

spotify_next is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit spotify_next? +

Yes. Add a rate_limit block to the spotify_next 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.

How do I block spotify_next completely? +

Set action: deny in the PolicyLayer policy for spotify_next. 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.

What MCP server provides spotify_next? +

spotify_next 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.