get_artist_radio
AI agents call get_artist_radio 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.
The 'get_' prefix and alignment with other read-only sibling tools indicate this retrieves radio station data or recommendations for an artist. Although the description is empty, the naming pattern and server context (music streaming service) strongly suggest a data retrieval operation with no side effects. No modification, deletion, or financial transaction capability is implied.
From the tool's definition Tool name 'get_artist_radio' with 'get_' prefix and sibling tools like 'get_album', 'get_artist', 'get_artist_albums', 'get_artist_top_tracks' which are all retrieval operations; the TIDAL server context indicates music streaming queries with no destructive,…
Attacks that exploit this kind of access
get_artist_radio. 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 get_artist_radio: 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.
get_artist_radio 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_artist_radio 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_artist_radio. 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_artist_radio 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 →