Remove a track from user's favorites (unlike a track).
AI agents call remove_track_from_favorites 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 a track from favorites is a destructive action in the sense that it deletes a saved/favorited item. While the user could re-add the track later, the action itself irreversibly removes the current favorite association without a recovery mechanism, making it Destructive rather than Write. Severity is medium as it affects user data (favorites list) but is limited in blast radius.
From the tool's definition 'Remove a track from user's favorites (unlike a track)' — permanently removes the track from the favorites list
Attacks that exploit this kind of access
Remove a track from user's favorites (unlike a track). 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_track_from_favorites: 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_track_from_favorites 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_track_from_favorites 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_track_from_favorites. 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_track_from_favorites 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 →