Search for public playlists on TIDAL.
AI agents call search_playlists 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 queries publicly available playlist data. It retrieves information without creating, modifying, deleting, or executing code. There is no financial impact, no data destruction, and no side effects beyond returning search results. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name is 'search_playlists' and description states 'Search for public playlists on TIDAL.' The verb 'search' is a read operation that retrieves information without modification.
Attacks that exploit this kind of access
Search for public playlists on 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 search_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 Server. Nothing to install.
search_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 search_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 search_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.
search_playlists 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 →