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.
Deletion of playlists is an irreversible destructive action that cannot be undone. Even though the description is empty, the tool name unambiguously indicates permanent data removal. This ranks as Destructive rather than Execute because the operation itself (deletion) is inherently destructive regardless of arguments.
From the tool's definition Tool name is 'delete_tidal_playlist' which explicitly indicates deletion of a playlist. The sibling context shows this server manages TIDAL playlists (create_tidal_playlist, get_user_playlists, get_playlist_tracks), confirming this tool removes data…
Documented attack patterns abuse exactly the kind of access delete_tidal_playlist gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TIDAL MCP: My Custom Picks, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_tidal_playlist:
{
"version": "1",
"default": "deny",
"hide": [
"delete_tidal_playlist"
]
}delete_tidal_playlist disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
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 (yuhuacheng/tidal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 7 TIDAL MCP: My Custom Picks tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
7 TIDAL MCP: My Custom Picks tools catalogued and risk-classified — across an index of 42,500+ MCP servers.