AI agents call get_user_playlists 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 appears to retrieve playlist data from the user's TIDAL account with no side effects. While the description is uninformative, the naming convention and server context clearly indicate a read-only query operation. No data modification, deletion, or external execution occurs. Severity is low because unauthorized playlist discovery has minimal impact; confidence is slightly reduced due to the empty description.
From the tool's definition Tool name 'get_user_playlists' indicates retrieval of existing playlist data. Description is empty, but the sibling tools context (create/delete/recommend operations) and the function name strongly suggest this fetches or queries user playlist information…
Documented attack patterns abuse exactly the kind of access get_user_playlists 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_user_playlists:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_playlists": {}
}
}get_user_playlists 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_user_playlists. 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_user_playlists: 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_user_playlists 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_user_playlists 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_user_playlists. 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_user_playlists 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.