transfer_playback

Move playback to a different Spotify Connect device

SERVERSpotify SOURCE@novalux12/spotify-mcp

Critical RISK CLASS

Category Financial

Parameters 00 required

Recommended Approval-gatedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/transfer-playback.md

WHAT IT DOES

What transfer_playback does on Spotify

AI agents use transfer_playback to commit financial operations through Spotify, usually the final step of a payment, billing, or trading workflow. A call moves real money.

RISK

Why transfer_playback is rated Critical

transfer_playback moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs transfer_playback 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 transfer_playback, this is the rule to start with:

transfer_playback Approval-gated

Any call to transfer_playback is blocked until a human approves it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_playback": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

GATE THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about transfer_playback

What does the transfer_playback tool do? +

Move playback to a different Spotify Connect device. It is categorised as a Financial tool in the Spotify MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on transfer_playback? +

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

What risk level is transfer_playback? +

transfer_playback is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transfer_playback? +

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

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

transfer_playback 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 544 Spotify tools → Critical-risk tools on this server →

Across the catalogue

bridge_transfer on 0xaibridge →transfer_sites on A3plus → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern MCP payment tools →Human-in-the-loop →Tool call approval →