next_track · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What next_track does on Spotify MCP Server

AI agents invoke next_track 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.

WHY IT NEEDS A POLICY

Why next_track needs a policy

This tool triggers an external playback operation on Spotify — it controls media playback state by skipping to the next track. It's not a simple read, nor does it create/modify stored data or delete anything. It executes an action on an external system (the Spotify player), making 'Execute' the most appropriate category.

From the tool's definition Skip to the next track

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

next_track Rate-limited

next_track 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": {
    "next_track": {
      "limits": [
        {
          "counter": "next_track_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about next_track

What does the next_track tool do? +

Skip to the next track. 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.

How do I enforce a policy on next_track? +

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

What risk level is next_track? +

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

Can I rate-limit next_track? +

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

How do I block next_track completely? +

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

What MCP server provides next_track? +

next_track is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.