Delete a playlist from user's account.
AI agents call delete_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.
This tool permanently removes a playlist and its associated data from the user's TIDAL account. Deletion cannot be undone, making it irreversible. While the blast radius is scoped to a single playlist rather than the entire account, an AI agent misusing this tool could destroy user-created playlists, curated collections, or shared playlists without recovery.
From the tool's definition Tool name is 'delete_playlist' and description states 'Delete a playlist from user's account.' The verb 'delete' combined with the action of removing a playlist irreversibly indicates a destructive operation.
Attacks that exploit this kind of access
Delete a playlist from user's account. 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 delete_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.
delete_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_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_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_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 →