spotify_remove_track_from_library
Remove the current track from liked songs
This record as markdown: /tools/mukul975-mcp-windows-automation/spotify-remove-track-from-library.md
What spotify_remove_track_from_library does on Mcp Windows
AI agents call spotify_remove_track_from_library to permanently remove resources in Mcp Windows, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why spotify_remove_track_from_library is rated Critical
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
Attacks that exploit this kind of access
The rule that runs spotify_remove_track_from_library safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Windows, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spotify_remove_track_from_library, this is the rule to start with:
spotify_remove_track_from_library is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Windows, apply this rule, and every spotify_remove_track_from_library call is checked against it from then on.
Questions about spotify_remove_track_from_library
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.
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.
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.
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.
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.
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.
More on Mcp Windows, and thousands of servers like it.
Across the catalogue