New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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

SERVERSpotify SOURCE@novalux12/spotify-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about migrate_playback_positions

What does the migrate_playback_positions tool do? +

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.

How do I enforce a policy on migrate_playback_positions? +

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.

What risk level is migrate_playback_positions? +

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

Can I rate-limit migrate_playback_positions? +

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.

How do I block migrate_playback_positions completely? +

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.

What MCP server provides migrate_playback_positions? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Spotify's. Pull the full record:

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.