mb_search_recordings
Search for recordings/tracks on MusicBrainz.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mb-search-recordings.md
What mb_search_recordings does on UnClick
AI agents call mb_search_recordings to retrieve information from UnClick 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 | number | — | |
query | string | Yes | |
artist | string | — |
Parameters from the server's own tool schema.
Why mb_search_recordings is rated Low
This tool retrieves data from a public music database without altering any state. It is a read-only operation that returns search results, analogous to querying a search index. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—worst case would be resource exhaustion from excessive queries, which is low severity.
From the tool's definition Tool performs a search operation on MusicBrainz recordings/tracks database. The verb 'search' and the description 'search for recordings/tracks' indicate a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs mb_search_recordings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mb_search_recordings, this is the rule to start with:
mb_search_recordings 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 UnClick, apply this rule, and every mb_search_recordings call is checked against it from then on.
Questions about mb_search_recordings
Search for recordings/tracks on MusicBrainz. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mb_search_recordings accepts 3 parameters: limit, query, artist. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mb_search_recordings: 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 UnClick. Nothing to install.
mb_search_recordings 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 mb_search_recordings 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 mb_search_recordings. 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.
mb_search_recordings is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue