skip_next

Skip to the next track in the queue or context.

SERVERSpotify SOURCE@novalux12/spotify-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/skip-next.md

WHAT IT DOES

What skip_next does on Spotify

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

RISK

Why skip_next is rated High

Triggers an external playback operation on Spotify, changing the current track.

From the tool's definition Skip to the next track in the queue or context

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs skip_next safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For skip_next, this is the rule to start with:

skip_next Rate-limited

skip_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": {
    "skip_next": {
      "limits": [
        {
          "counter": "skip_next_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every skip_next call is checked against it from then on.

FAQ

Questions about skip_next

What does the skip_next tool do? +

Skip to the next track in the queue or context. 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 skip_next? +

Register the Spotify MCP server in PolicyLayer and add a rule for skip_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 skip_next? +

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

Can I rate-limit skip_next? +

Yes. Add a rate_limit block to the skip_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 skip_next completely? +

Set action: deny in the PolicyLayer policy for skip_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 skip_next? +

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

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →