music.releases.details

Get full release details by MusicBrainz ID — artist credits, labels, media formats (MusicBrainz)

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/music.releases.details.md

WHAT IT DOES

What music.releases.details does on Apibase

AI agents call music.releases.details 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
`mbid`	string	Yes	MusicBrainz release ID (UUID format). Returns artist credits and label info

Parameters from the server's own tool schema.

RISK

Why music.releases.details is rated Low

Retrieves music metadata with no side effects or data modification capabilities.

From the tool's definition Get full release details, artist credits, labels, media formats

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs music.releases.details 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.releases.details, this is the rule to start with:

music.releases.details Allowed

music.releases.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "music.releases.details": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every music.releases.details call is checked against it from then on.

FAQ

Questions about music.releases.details

What does the music.releases.details tool do? +

Get full release details by MusicBrainz ID — artist credits, labels, media formats (MusicBrainz). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does music.releases.details accept? +

music.releases.details accepts 1 parameter: mbid. Required: mbid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on music.releases.details? +

Register the Apibase MCP server in PolicyLayer and add a rule for music.releases.details: 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.

What risk level is music.releases.details? +

music.releases.details is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit music.releases.details? +

Yes. Add a rate_limit block to the music.releases.details 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.

How do I block music.releases.details completely? +

Set action: deny in the PolicyLayer policy for music.releases.details. 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.

What MCP server provides music.releases.details? +

music.releases.details 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →