delete_playback_bookmark

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/delete-playback-bookmark.md

WHAT IT DOES

What delete_playback_bookmark does on Spotify

AI agents call delete_playback_bookmark 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 delete_playback_bookmark is rated Critical

Irreversibly deletes user data without recovery option, though blast radius limited to single bookmark.

From the tool's definition Delete one saved playback position, whichever it came from. Commits by default.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_playback_bookmark 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 delete_playback_bookmark, this is the rule to start with:

delete_playback_bookmark Hidden

delete_playback_bookmark 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": [
    "delete_playback_bookmark"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about delete_playback_bookmark

What does the delete_playback_bookmark tool do? +

Delete one saved playback position — a capture_playback_position bookmark, an exhaust2 checkpoint or a playback-ext state, whichever it came from. Commits by default — pass dry_run=true to preview. 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 delete_playback_bookmark? +

Register the Spotify MCP server in PolicyLayer and add a rule for delete_playback_bookmark: 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 delete_playback_bookmark? +

delete_playback_bookmark 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 delete_playback_bookmark? +

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

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

delete_playback_bookmark 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →