music.radio.search
Search 40K+ internet radio stations by name, genre, country, or language — streaming URLs, bitrate, codec (RadioBrowser)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/music.radio.search.md
What music.radio.search does on Apibase
AI agents call music.radio.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Tag/genre filter (e.g. "rock", "jazz", "classical", "news") |
name | string | — | Station name to search for (e.g. "BBC Radio", "Jazz FM") |
limit | integer | — | Max stations to return (1-100, default 25) |
order | string | — | Sort order for results |
country | string | — | Country name filter (e.g. "Germany", "United States") |
language | string | — | Language filter (e.g. "english", "german", "spanish") |
hidebroken | boolean | — | Hide broken/offline stations (recommended: true) |
countrycode | string | — | ISO 3166-1 alpha-2 country code (e.g. "US", "DE", "GB") |
Parameters from the server's own tool schema.
Why music.radio.search is rated Low
Queries public radio station metadata; returns informational data without side effects or capabilities.
From the tool's definition Search 40K+ internet radio stations, streaming URLs, bitrate, codec
Attacks that exploit this kind of access
The rule that runs music.radio.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For music.radio.search, this is the rule to start with:
music.radio.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every music.radio.search call is checked against it from then on.
Questions about music.radio.search
Search 40K+ internet radio stations by name, genre, country, or language — streaming URLs, bitrate, codec (RadioBrowser). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
music.radio.search accepts 8 parameters: tag, name, limit, order, country, language, hidebroken, countrycode. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for music.radio.search: 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 Apibase. Nothing to install.
music.radio.search 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 music.radio.search 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 music.radio.search. 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.
music.radio.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue