get_playlist_tracks
AI agents call get_playlist_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 lists tracks from a playlist—a read operation with no side effects. Empty description lowers confidence slightly, but the get_ prefix and context with other TIDAL playlist management tools clearly indicate data retrieval. No creation, deletion, execution, financial transaction, or irreversible action is implied.
From the tool's definition Tool name 'get_playlist_tracks' combined with server context indicates retrieval of playlist track data. Description is empty, but naming convention (get_*) and sibling tools (create_tidal_playlist, delete_tidal_playlist, get_favorite_tracks,…
Attacks that exploit this kind of access
get_playlist_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_playlist_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_playlist_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_playlist_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_playlist_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_playlist_tracks is provided by the TIDAL MCP: My Custom Picks MCP server (mikeysrecipes/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 →