music.audd.recognize
Identify a song from an audio file URL — like Shazam for AI agents. Analyzes audio fingerprint against 80M+ tracks and returns artist, title, album, release date, plus Spotify and Apple Music links. Accepts MP3, WAV, OGG, or any audio URL (AudD)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/music.audd.recognize.md
What music.audd.recognize does on Apibase
AI agents call music.audd.recognize 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 |
|---|---|---|---|
url | string | Yes | URL of audio file to identify (MP3, WAV, OGG, etc.). The API analyzes the audio and matches it against 80M+ tracks. Example: "https://example.com/song.mp3" |
Parameters from the server's own tool schema.
Why music.audd.recognize is rated Low
Tool queries a music database and returns metadata with no side effects or mutations.
From the tool's definition Identify a song from an audio file URL; analyzes audio fingerprint; returns metadata.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs music.audd.recognize 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.audd.recognize, this is the rule to start with:
music.audd.recognize 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.audd.recognize call is checked against it from then on.
Questions about music.audd.recognize
Identify a song from an audio file URL — like Shazam for AI agents. Analyzes audio fingerprint against 80M+ tracks and returns artist, title, album, release date, plus Spotify and Apple Music links. Accepts MP3, WAV, OGG, or any audio URL (AudD). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
music.audd.recognize accepts 1 parameter: url. Required: url. 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.audd.recognize: 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.audd.recognize 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.audd.recognize 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.audd.recognize. 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.audd.recognize 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