music.recording

Resolve a song/recording from MusicBrainz (open, CC0 music encyclopedia). Pass artist + title, or a free-text/Lucene query. Returns ranked recordings with MBID, title, primary artist, length (ms), first-release date, disambiguation. Keyless, public-domain. Canonicalize a track to its MBID.

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.recording.md

WHAT IT DOES

What music.recording does on Mcp

AI agents call music.recording 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.recording is rated Low

This tool queries a public music encyclopedia (MusicBrainz) to retrieve metadata about recordings. It accepts search parameters (artist, title, or query) and returns structured data (MBID, title, artist, length, release date, disambiguation). No data is created, modified, deleted, or used to trigger external operations.

From the tool's definition Tool description specifies it 'Resolve[s] a song/recording from MusicBrainz' and 'Returns ranked recordings with MBID, title, primary artist, length (ms), first-release date, disambiguation.' These are pure read/query operations that retrieve and return data…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

music.recording Allowed

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

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.recording call is checked against it from then on.

FAQ

Questions about music.recording

What does the music.recording tool do? +

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

Register the MCP server in PolicyLayer and add a rule for music.recording: 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.recording? +

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

Can I rate-limit music.recording? +

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

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

music.recording 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 →