// SCAN REPORT

Apple Music MCP Server

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

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

Last updated: 30 Jun 2026

3 can modify or destroy data

6 read-only

9 tools total

Community server · catalogue entry verified 30/06/2026

How to control Apple Music MCP Server ↓

TOOL MAP

What Apple Music MCP Server exposes to your agents

Read (6) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Apple Music MCP Server tools

Destructive · Medium remove_tracks_from_playlist Removing tracks from a playlist is a destructive action — once removed, the track associations are lost and cannot be automatically restored. Write · Low add_tracks_to_playlist This tool modifies playlist data by adding tracks, which is a reversible write operation. Write · Low create_playlist Creating a playlist is a reversible data modification operation.

3 of Apple Music MCP Server's 9 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Apple Music MCP Server

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

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_library_songs": {
    "limits": [
      {
        "counter": "get_library_songs_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 Apple Music MCP Server — 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 APPLE MUSIC →

Instant setup, no code required.

FULL CATALOGUE

All 9 Apple Music MCP Server tools

DESTRUCTIVE 1 tools

Destructive remove_tracks_from_playlist Remove tracks from a playlist. Note: Apple Music API has limited support for track removal - this may not work

WRITE 2 tools

Write add_tracks_to_playlist Add tracks to an existing playlist in the user Write create_playlist Create a new playlist in the user

READ 6 tools

Read get_library_songs Get songs from the user Read get_playlist_tracks Get the tracks in a specific playlist from the user Read get_recently_played Get the user Read get_recommendations Get personalized music recommendations from Apple Music based on listening history Read get_user_playlists List all playlists from the user Read search_music Search the Apple Music catalog for songs, albums, artists, and playlists

EXPLORE

Related servers

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

FAQ

Questions about Apple Music MCP Server

Can an AI agent delete data through the Apple Music MCP Server MCP server? +

Yes. The Apple Music MCP 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 Apple Music MCP Server? +

The Apple Music MCP Server server has 2 write tools including add_tracks_to_playlist, create_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 Apple Music MCP Server.

How many tools does the Apple Music MCP Server MCP server expose? +

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

How do I enforce a policy on Apple Music MCP Server? +

Register the Apple Music 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 Apple Music MCP Server tool call.

Deterministic rules across all 9 Apple Music MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON APPLE MUSIC →

Instant setup, no code required.

9 Apple Music MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.