add_playlist_items · Spotify MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_playlist_items does on Spotify MCP Server

AI agents use add_playlist_items to create or update resources in Spotify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spotify MCP Server environment.

WHY IT NEEDS A POLICY

Why add_playlist_items needs a policy

Adding items to a playlist creates or modifies data (the playlist contents) reversibly—items can be removed later. This is a Write operation, not Destructive (since it's reversible), and carries medium severity since misuse could spam playlists or add unwanted content, but the impact is limited to playlist state and user experience rather than data loss or financial harm.

From the tool's definition Tool name 'add_playlist_items' indicates modifying playlist contents by adding items. Sibling tools like 'create_playlist', 'follow_playlist', and context that this server manages 'playlists' confirm this is a write operation that creates or modifies data…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_playlist_items Rate-limited

add_playlist_items stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_playlist_items": {
      "limits": [
        {
          "counter": "add_playlist_items_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Spotify MCP Server, so you can run agents against it safely.

FAQ

Questions about add_playlist_items

What does the add_playlist_items tool do? +

add_playlist_items. It is categorised as a Write tool in the Spotify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_playlist_items? +

Register the Spotify MCP Server MCP server in PolicyLayer and add a rule for add_playlist_items: 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 MCP Server. Nothing to install.

What risk level is add_playlist_items? +

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

Can I rate-limit add_playlist_items? +

Yes. Add a rate_limit block to the add_playlist_items 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 add_playlist_items completely? +

Set action: deny in the PolicyLayer policy for add_playlist_items. 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 add_playlist_items? +

add_playlist_items is provided by the Spotify MCP Server MCP server (llyfn/spotify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.