spotify_transfer_playback · Spotify MCP Server MCP

WHAT IT DOES

What spotify_transfer_playback does on Spotify MCP Server

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

This tool triggers an external operation on Spotify's playback system by redirecting active playback to a different device. It doesn't merely read data, nor does it create/modify stored content — it executes a stateful command that changes the active playback device. The blast radius is medium: misuse could disrupt active listening sessions but causes no irreversible data loss or financial impact.

From the tool's definition Transfer playback to a different device

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

spotify_transfer_playback Rate-limited

spotify_transfer_playback 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_transfer_playback": {
      "limits": [
        {
          "counter": "spotify_transfer_playback_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 spotify_transfer_playback

What does the spotify_transfer_playback tool do? +

Transfer playback to a different device. 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 spotify_transfer_playback? +

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

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

Can I rate-limit spotify_transfer_playback? +

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

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

spotify_transfer_playback 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_transfer_playback 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 →