// SCAN REPORT

Spotify

46 tools. 17 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 30 Aug 2026

17 can modify or destroy data

29 read-only

46 tools total

Community server · catalogue entry checked 05/04/2026 · full schemas captured for 43 of 46 tools

How to control Spotify ↓

TOOL MAP

What Spotify exposes to your agents

Read (29) Write / Execute (15) Destructive / Financial (2)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Spotify costs in tokens

11,357 tokens of tool definitions, loaded on every request

5.7% of a 200k context window

684 heaviest tool: search.list

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Spotify tools

Destructive · High me.library.delete The tool performs irreversible deletion of user library items (tracks, albums, episodes, shows, audiobooks, playlists). Destructive · High playlists.items.delete The tool explicitly removes items from a playlist, which is an irreversible deletion action (items are removed from the playlist). Execute · Medium me.player.play.update This tool executes a command that controls the user's Spotify playback on their device. Execute · Medium me.player.next.create This tool triggers an external playback operation on Spotify's player — it changes the playback state by skipping to the next track.

17 of Spotify's 46 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Spotify

PolicyLayer is an MCP gateway — it sits between your AI agents and Spotify, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "me.library.delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "me.library.update": {
    "limits": [
      {
        "counter": "me.library.update_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "albums.get": {
    "limits": [
      {
        "counter": "albums.get_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Spotify — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SPOTIFY →

Instant setup, no code required.

FULL CATALOGUE

All 46 Spotify tools

DESTRUCTIVE 2 tools

Destructive me.library.delete Remove one or more items from the current user's library. Accepts Spotify URIs for tracks, albums, episodes, s Destructive playlists.items.delete Remove one or more items from a user's playlist.

EXECUTE 6 tools

Execute me.player.next.create Skips to next track in the user’s queue. This API only works for users who have Spotify Premium. The order of Execute me.player.pause.update Pause playback on the user's account. This API only works for users who have Spotify Premium. The order of exe Execute me.player.play.update Start a new context or resume current playback on the user's active device. This API only works for users who Execute me.player.previous.create Skips to previous track in the user’s queue. This API only works for users who have Spotify Premium. The order Execute me.player.seek.update Seeks to the given position in the user’s currently playing track. This API only works for users who have Spot Execute me.player.update Transfer playback to a new device and optionally begin playback. This API only works for users who have Spotif

WRITE 9 tools

Write me.library.update Add one or more items to the current user's library. Accepts Spotify URIs for tracks, albums, episodes, shows, Write me.player.queue.create Add an item to be played next in the user's current playback queue. This API only works for users who have Spo Write me.player.repeat.update Set the repeat mode for the user's playback. This API only works for users who have Spotify Premium. The order Write me.player.shuffle.update Toggle shuffle on or off for user’s playback. This API only works for users who have Spotify Premium. The orde Write me.player.volume.update Set the volume for the user’s current playback device. This API only works for users who have Spotify Premium. Write me.playlists.create Create a playlist for the current Spotify user. (The playlist will be empty until you [add tracks](/documentat Write playlists.items.create Add one or more items to a user's playlist. Write playlists.items.update Either reorder or replace items in a playlist depending on the request's parameters. To reorder items, include Write playlists.update Change a playlist's name and public/private state. (The user must, of course, own the playlist.)

READ 29 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Spotify

Can an AI agent delete data through the Spotify MCP server? +

Yes. The Spotify server exposes 2 destructive tools including me.library.delete, playlists.items.delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Spotify? +

The Spotify server has 9 write tools including me.library.update, me.player.queue.create, me.player.repeat.update. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Spotify.

How many tools does the Spotify MCP server expose? +

46 tools across 4 categories: Destructive, Execute, Read, Write. 29 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on Spotify? +

Register the Spotify MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Spotify tool call.

Deterministic rules across all 46 Spotify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SPOTIFY →

Instant setup, no code required.

46 Spotify tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Spotify's registry record.

The record behind this page: 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 →