delete_tidal_playlist
AI agents call delete_tidal_playlist to permanently remove resources in TIDAL MCP: My Custom Picks — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool deletes playlists from a user's TIDAL account. Playlist deletion is destructive because it permanently removes user-created content and cannot be reversed. Although the description is empty, the name and server context make the destructive intent unambiguous. Severity is high rather than critical because the impact is limited to one user's playlists rather than system-wide data or financial harm.
From the tool's definition Tool name explicitly contains 'delete' applied to a playlist resource. In context of a TIDAL music account, deletion of playlists is an irreversible action that cannot be undone.
Attacks that exploit this kind of access
delete_tidal_playlist. It is categorised as a Destructive tool in the TIDAL MCP: My Custom Picks MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TIDAL MCP: My Custom Picks MCP server in PolicyLayer and add a rule for delete_tidal_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: My Custom Picks. Nothing to install.
delete_tidal_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 delete_tidal_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 delete_tidal_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.
delete_tidal_playlist is provided by the TIDAL MCP: My Custom Picks MCP server (mikeysrecipes/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 →