Your Spotify MCP Server

28 tools. 11 can modify or destroy data without limits.

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

Last updated:

11 can modify or destroy data
17 read-only
28 tools total

Community server · catalogue entry verified 03/07/2026

How to control Your Spotify MCP Server ↓

What Your Spotify MCP Server exposes to your agents

Read (17) Write / Execute (9) Destructive / Financial (2)
Critical Risk

The most dangerous Your Spotify MCP Server tools

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

How to control Your Spotify MCP Server

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

Deny destructive operations
{
  "remove_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
{
  "analyze_affinity": {
    "limits": [
      {
        "counter": "analyze_affinity_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Your Spotify MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON YOUR SPOTIFY →

Instant setup, no code required.

All 28 Your Spotify MCP Server tools

READ 17 tools
Read analyze_affinity Analyze listening overlap between multiple Your Spotify users. Find songs that multiple users share in common Read analyze_listening_patterns Analyze your listening patterns over time. Discover when you listen to music most - by hour of day, day of we Read compare_listening_periods Compare your listening habits between two time periods. See how your listening volume, diversity, and prefere Read create_custom_wrapped Generate a custom Spotify Wrapped summary for ANY time period. Unlike Spotify Read export_listening_data Export your listening data in various formats. Get a structured export of your listening history, top tracks, Read get_artist_rank Find where a specific artist ranks in your listening history. Shows the artist Read get_artist_stats Get detailed listening statistics for a specific artist from your listening history. Returns information incl Read get_current_playback Get information about what Read get_discovery_insights Discover new music you found in a specific time period. Shows tracks and artists you listened to for the firs Read get_listening_timeline Analyze your listening activity over time. Returns a timeline of plays and listening duration at day, week, o Read get_top_artists Get your top artists for a specified time period. Returns artists ranked by play count including: - Artist na Read get_top_tracks Get your most played tracks for any time period. Returns your top tracks ranked by play count, with full trac Read get_track_rank Find where a specific track ranks in your listening history. Shows the track Read get_track_stats Get detailed listening statistics for a specific track from your listening history. Returns information inclu Read get_user_playlists Get a list of your Spotify playlists. Returns playlist names, IDs, track counts, and whether they Read search_listening_history Search through your complete Spotify listening history. Unlike Spotify Read search_spotify_catalog Search Spotify

Related servers

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

Questions about Your Spotify MCP Server

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

Yes. The Your Spotify MCP Server server exposes 2 destructive tools including remove_from_playlist, revoke_public_access. 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 Your Spotify MCP Server? +

The Your Spotify MCP Server server has 7 write tools including add_tracks_to_playlist, create_playlist_from_query, generate_public_share_link. 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 Your Spotify MCP Server.

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

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

How do I enforce a policy on Your Spotify MCP Server? +

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

Enforce policy on every Your Spotify MCP Server tool call.

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

Instant setup, no code required.

28 Your Spotify MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.