music.recordings.search
Search for songs and recordings by title or artist — duration, release history, artist credits (MusicBrainz)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/music.recordings.search.md
What music.recordings.search does on Apibase
AI agents call music.recordings.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 |
|---|---|---|---|
limit | integer | — | Max results to return (1-100, default 25) |
query | string | Yes | Search query for song/recording title (e.g. "Creep", "So What"). Supports Lucene syntax: artist:"Radiohead" AND recording:"Creep" |
offset | integer | — | Pagination offset for results |
Parameters from the server's own tool schema.
Why music.recordings.search is rated Low
Tool retrieves music metadata from MusicBrainz with no side effects or data modification.
From the tool's definition Search for songs and recordings by title or artist
Attacks that exploit this kind of access
The rule that runs music.recordings.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.recordings.search, this is the rule to start with:
music.recordings.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.recordings.search call is checked against it from then on.
Questions about music.recordings.search
Search for songs and recordings by title or artist — duration, release history, artist credits (MusicBrainz). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
music.recordings.search accepts 3 parameters: limit, query, offset. Required: query. 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.recordings.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.recordings.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.recordings.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.recordings.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.recordings.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