spotify_set_shuffle · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What spotify_set_shuffle does on Spotify MCP Server

AI agents use spotify_set_shuffle to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.

WHY IT NEEDS A POLICY

Why spotify_set_shuffle needs a policy

This tool modifies Spotify playback settings in a reversible manner. The user can toggle shuffle back to its previous state at any time. While it affects the user's listening experience, it causes no data loss, financial impact, or irreversible consequences.

From the tool's definition Tool name is 'spotify_set_shuffle' and description states 'Toggle shuffle mode on or off.' This modifies playback settings but does not create or delete data persistently; it changes a reversible state (shuffle enabled/disabled).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_set_shuffle Rate-limited

spotify_set_shuffle stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_set_shuffle": {
      "limits": [
        {
          "counter": "spotify_set_shuffle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 spotify_set_shuffle

What does the spotify_set_shuffle tool do? +

Toggle shuffle mode on or off. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on spotify_set_shuffle? +

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

spotify_set_shuffle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit spotify_set_shuffle? +

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

Set action: deny in the PolicyLayer policy for spotify_set_shuffle. 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_set_shuffle? +

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

// THE FULL RECORD

spotify_set_shuffle is one line of Spotify MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →