toggle_shuffle · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What toggle_shuffle does on Spotify MCP Server

AI agents invoke toggle_shuffle 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 toggle_shuffle needs a policy

This tool triggers an external operation on the Spotify playback system by changing the shuffle state. It doesn't read data, write persistent data, destroy anything, or involve finances — it controls playback behavior, making Execute the most appropriate category. The blast radius is low as it only affects the shuffle setting of the current playback session.

From the tool's definition 'Set or toggle shuffle mode for playback'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

toggle_shuffle Rate-limited

toggle_shuffle 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": {
    "toggle_shuffle": {
      "limits": [
        {
          "counter": "toggle_shuffle_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 toggle_shuffle

What does the toggle_shuffle tool do? +

Set or toggle shuffle mode for playback. 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 toggle_shuffle? +

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

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

Can I rate-limit toggle_shuffle? +

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

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

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