music.audd.lyrics
Search for song lyrics by artist name, song title, or both. Returns full lyrics text, artist, title, and metadata. Query examples: "imagine john lennon", "bohemian rhapsody", "taylor swift love story" (AudD)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/music.audd.lyrics.md
What music.audd.lyrics does on Apibase
AI agents call music.audd.lyrics 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 |
|---|---|---|---|
q | string | Yes | Search query for lyrics — artist name, song title, or both (e.g. "imagine john lennon", "bohemian rhapsody", "taylor swift love story") |
Parameters from the server's own tool schema.
Why music.audd.lyrics is rated Low
Tool queries and retrieves lyrics data without modifying, executing code, or creating obligations.
From the tool's definition Search for song lyrics, returns full lyrics text, artist, title, metadata.
Attacks that exploit this kind of access
The rule that runs music.audd.lyrics 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.lyrics, this is the rule to start with:
music.audd.lyrics 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.lyrics call is checked against it from then on.
Questions about music.audd.lyrics
Search for song lyrics by artist name, song title, or both. Returns full lyrics text, artist, title, and metadata. Query examples: "imagine john lennon", "bohemian rhapsody", "taylor swift love story" (AudD). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
music.audd.lyrics accepts 1 parameter: q. Required: q. 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.lyrics: 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.lyrics 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.lyrics 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.lyrics. 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.lyrics 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