music.release

Resolve an album/release from MusicBrainz (CC0). Pass a barcode (UPC/EAN), artist + album, or a free-text query. Returns ranked releases with MBID, title, artist, date, country, barcode, status, track count, label, catalog number. Barcode → album is the differentiated lookup. Keyless, public-domain.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/music.release.md

WHAT IT DOES

What music.release does on Mcp

AI agents call music.release to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why music.release is rated Low

This is a pure data retrieval tool that queries MusicBrainz and returns structured information about music releases. The operations described (resolve, pass query, return data) are all read-only with no side effects. No data is modified, deleted, executed, or used to move funds. The blast radius of misuse is minimal—an agent cannot harm systems or data by repeatedly querying public music metadata.

From the tool's definition Tool 'resolves' and 'returns' album/release data from MusicBrainz. No creation, modification, deletion, code execution, or financial transaction is performed.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs music.release safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For music.release, this is the rule to start with:

music.release Allowed

music.release 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.release": {}
  }
}

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

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

FAQ

Questions about music.release

What does the music.release tool do? +

How do I enforce a policy on music.release? +

Register the MCP server in PolicyLayer and add a rule for music.release: 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 Mcp. Nothing to install.

What risk level is music.release? +

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

Can I rate-limit music.release? +

Yes. Add a rate_limit block to the music.release 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.release completely? +

Set action: deny in the PolicyLayer policy for music.release. 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.release? +

music.release is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

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