AI agents call recommend_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.
The tool is named 'recommend_tracks', which typically retrieves or suggests data based on criteria without modifying any state. The server description mentions 'get customized music recommendations', confirming this is a retrieval function.
From the tool's definition Tool name 'recommend_tracks' indicates retrieval of music recommendations. Sibling tools show this server has both read operations (get_favorite_tracks, get_playlist_tracks, get_user_playlists) and write operations (create_tidal_playlist,…
Documented attack patterns abuse exactly the kind of access recommend_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 recommend_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"recommend_tracks": {}
}
}recommend_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.
recommend_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 recommend_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.
recommend_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 recommend_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 recommend_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.
recommend_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.