remove_tracks_from_playlist
AI agents call remove_tracks_from_playlist to permanently remove resources in TIDAL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing tracks from a playlist is a destructive operation as it deletes data (track associations) from the playlist. While the tracks themselves are not deleted, the removal from the playlist may be irreversible depending on the implementation. Given the naming pattern and context of sibling tools (delete_playlist, add_tracks_to_playlist), this tool performs a destructive modification.
From the tool's definition Tool name 'remove_tracks_from_playlist' implies irreversible removal of tracks from a playlist; description is empty providing no additional context.
Attacks that exploit this kind of access
remove_tracks_from_playlist. It is categorised as a Destructive tool in the TIDAL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TIDAL MCP Server MCP server in PolicyLayer and add a rule for remove_tracks_from_playlist: 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 TIDAL MCP Server. Nothing to install.
remove_tracks_from_playlist 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 remove_tracks_from_playlist 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 remove_tracks_from_playlist. 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.
remove_tracks_from_playlist is provided by the TIDAL MCP Server MCP server (keenanbb/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →