AI agents call get_favorite_tracks to retrieve information from TIDAL MCP: My Custom Picks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries favorite tracks from a user's TIDAL account with no side effects—no creation, deletion, or modification of data. The naming convention aligns with other 'get_' tools on the server (get_playlist_tracks, get_user_playlists) which are clearly read operations. Confidence is slightly lower due to empty description, but context strongly supports a Read categorization.
From the tool's definition Tool name 'get_favorite_tracks' indicates retrieval of user data without modification. Description is empty, but name and sibling tools (create_tidal_playlist, delete_tidal_playlist, get_playlist_tracks, get_user_playlists) in context suggest this is a read…
Documented attack patterns abuse exactly the kind of access get_favorite_tracks 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 get_favorite_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"get_favorite_tracks": {}
}
}get_favorite_tracks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_favorite_tracks. It is categorised as a Read tool in the TIDAL MCP: My Custom Picks MCP Server, which means it retrieves data without modifying state.
Register the TIDAL MCP: My Custom Picks 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: My Custom Picks. 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: 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.