playlist_remove_artist

Remove every track by one artist from a playlist. The reference is matched against every credited

SERVERSpotify SOURCE@novalux12/spotify-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/novalux12-spotify-mcp/playlist-remove-artist.md

WHAT IT DOES

What playlist_remove_artist does on Spotify

AI agents call playlist_remove_artist to permanently remove resources in Spotify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why playlist_remove_artist is rated Critical

Bulk removes tracks from a playlist, potentially irreversible without manual re-addition.

From the tool's definition Remove every track by one artist from a playlist

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs playlist_remove_artist safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Spotify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For playlist_remove_artist, this is the rule to start with:

playlist_remove_artist Hidden

playlist_remove_artist is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "playlist_remove_artist"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Spotify, apply this rule, and every playlist_remove_artist call is checked against it from then on.

FAQ

Questions about playlist_remove_artist

What does the playlist_remove_artist tool do? +

Remove every track by one artist from a playlist. The reference is matched against every credited. It is categorised as a Destructive tool in the Spotify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on playlist_remove_artist? +

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

What risk level is playlist_remove_artist? +

playlist_remove_artist is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit playlist_remove_artist? +

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

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

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

KEEP EXPLORING

More on Spotify, and thousands of servers like it.

This server

All 538 Spotify tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →