migrate_playback_positions
One-time, idempotent import of every legacy playback position (exhaust2 checkpoints, playback-ext states, backup-dir bookmarks) into the single canonical record. Running it twice changes no record and imports zero. A legacy store that exists but cannot be parsed is refused with nothing written, a...
This record as markdown: /tools/novalux12-spotify-mcp/migrate-playback-positions.md
What migrate_playback_positions does on Spotify
AI agents use migrate_playback_positions to create or update resources in Spotify, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify environment.
Why migrate_playback_positions is rated Medium
Modifies playback position data reversibly; idempotent design and preservation safeguards reduce severity below destructive.
From the tool's definition import of legacy playback position, idempotent, writes to canonical record
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs migrate_playback_positions 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 migrate_playback_positions, this is the rule to start with:
migrate_playback_positions 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every migrate_playback_positions call is checked against it from then on.
Questions about migrate_playback_positions
One-time, idempotent import of every legacy playback position (exhaust2 checkpoints, playback-ext states, backup-dir bookmarks) into the single canonical record. Running it twice changes no record and imports zero. A legacy store that exists but cannot be parsed is refused with nothing written, and its bytes are preserved. Legacy bookmark files are renamed to .migrated, never deleted. It is categorised as a Write tool in the Spotify MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spotify MCP server in PolicyLayer and add a rule for migrate_playback_positions: 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.
migrate_playback_positions is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the migrate_playback_positions 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.
Set action: deny in the PolicyLayer policy for migrate_playback_positions. 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.
migrate_playback_positions 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.
More on Spotify, and thousands of servers like it.
This server
Across the catalogue