spotify_remove_track_from_library

THE RISK

Critical Risk

Removing a track from liked songs/library is a deletion action that removes a saved item. While it may be reversible by re-liking the track, it irreversibly removes the user's curation/preference state without an undo mechanism in the API context. The action is a removal/deletion operation on user library data.

From the tool's definition Remove the current track from liked songs

Documented attack patterns abuse exactly the kind of access spotify_remove_track_from_library gives an agent:

HOW TO CONTROL SPOTIFY_REMOVE_TRACK_FROM_LIBRARY

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for spotify_remove_track_from_library:

policy.json

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

spotify_remove_track_from_library disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Mcp Windows — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Mcp Windows tools

Destructive clean_empty_directories Remove empty directories recursively Destructive drop_event Drop a scheduled event. Destructive drop_partition Drop a partition from a table. Destructive drop_role Drop a role (MySQL 8.0+). Destructive drop_stored_function Drop a stored function. Destructive drop_stored_procedure Drop a stored procedure. Destructive event_log_clear Clear a Windows Event Log (requires admin privileges) Destructive mysql_delete_data Delete data from a table.

All 441 Mcp Windows tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Mcp Windows → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the spotify_remove_track_from_library tool do? +

Remove the current track from liked songs. It is categorised as a Destructive tool in the Mcp Windows 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 spotify_remove_track_from_library? +

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

What risk level is spotify_remove_track_from_library? +

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

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

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

spotify_remove_track_from_library is provided by the Mcp Windows MCP server (mukul975/mcp-windows-automation). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Windows tool call.

Deterministic rules across all 441 Mcp Windows tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN MCP WINDOWS →

Free to start. No card required.

441 Mcp Windows tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

spotify_remove_track_from_library

// WHAT SPOTIFY_REMOVE_TRACK_FROM_LIBRARY ON MCP WINDOWS DOES

// THE RISK

// HOW TO CONTROL SPOTIFY_REMOVE_TRACK_FROM_LIBRARY

// EXPLORE