get_track_radio
AI agents call get_track_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 tool retrieves or queries radio data/recommendations related to a track, producing no side effects, data modifications, deletions, or financial transactions. While the empty description introduces minor uncertainty, the sibling tool 'get_artist_radio' and the consistent 'get_*' naming convention strongly suggest this is a non-destructive read operation.
From the tool's definition Tool name 'get_track_radio' indicates retrieval of radio content or recommendations based on a track. No description provided, but naming pattern matches sibling read operations like 'get_artist_radio', 'get_artist_albums', 'get_artist_top_tracks', which are…
Attacks that exploit this kind of access
get_track_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_track_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_track_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_track_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_track_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_track_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 →