Get user's favorite (liked) tracks from TIDAL.
AI agents call get_favorite_tracks to retrieve information from TIDAL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user preference data (favorite/liked tracks) without creating, modifying, or deleting any information. It is a pure read operation similar to fetching or querying a list. The blast radius of misuse is minimal—an AI agent could only retrieve the user's music preferences, which poses no financial, destructive, or operational risk.
From the tool's definition Tool name 'get_favorite_tracks' and description 'Get user's favorite (liked) tracks from TIDAL' indicate retrieval of existing data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Get user's favorite (liked) tracks from TIDAL. It is categorised as a Read tool in the TIDAL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TIDAL MCP Server MCP server in PolicyLayer and add a rule for get_favorite_tracks: 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.
get_favorite_tracks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_favorite_tracks 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 get_favorite_tracks. 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.
get_favorite_tracks 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 →