Spotify Server

26 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

3 can modify or destroy data
23 read-only
26 tools total

3 Spotify Server tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SPOTIFY SERVER →

Free to start. No card required.

Read (23) Write / Execute (2) Destructive / Financial (1)
2,306 tokens of tool definitions, loaded on every request
1.2% of a 200k context window
144 heaviest tool: get_artist_albums

Destructive tools (remove_tracks_from_playlist) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (add_tracks_to_playlist, modify_playlist) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Deny destructive operations
{
  "remove_tracks_from_playlist": {
    "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
{
  "add_tracks_to_playlist": {
    "limits": [
      {
        "counter": "add_tracks_to_playlist_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_access_token": {
    "limits": [
      {
        "counter": "get_access_token_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

Get this policy live on your own Spotify Server server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY SPOTIFY SERVER →
Can an AI agent delete data through the Spotify Server MCP server? +

Yes. The Spotify Server server exposes 1 destructive tools including remove_tracks_from_playlist. 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 Server? +

The Spotify Server server has 2 write tools including add_tracks_to_playlist, modify_playlist. 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 Server.

How many tools does the Spotify Server MCP server expose? +

26 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Spotify Server? +

Register the Spotify Server 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.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every Spotify Server tool call.

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

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.