get_album_tracks

List all tracks on a TheAudioDB album by its idAlbum (as returned by search_album). Returns each track id, title, track number, duration in milliseconds, genre, and music-video URL when available.

Server Mcp Theaudiodb https://gateway.pipeworx.io/theaudiodb/mcp
Category Read
Risk class Low
Parameters 11 required

What get_album_tracks does on Mcp Theaudiodb

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

ParameterTypeRequiredDescription
album_id string Yes TheAudioDB idAlbum, e.g. "2109615".

Parameters from the server's own tool schema.

Why get_album_tracks needs a policy

This tool retrieves read-only metadata from TheAudioDB about album tracks. It takes an idAlbum parameter and returns structured information (track IDs, titles, durations, genre, video URLs). There are no side effects, no data modification, no code execution, and no irreversible actions.

From the tool's definition The tool description explicitly states it 'List all tracks' and 'Returns each track id, title, track number, duration' — purely data retrieval operations with no modification, deletion, or execution capabilities.

Questions about get_album_tracks

What does the get_album_tracks tool do? +

List all tracks on a TheAudioDB album by its idAlbum (as returned by search_album). Returns each track id, title, track number, duration in milliseconds, genre, and music-video URL when available. It is categorised as a Read tool in the Mcp Theaudiodb MCP Server, which means it retrieves data without modifying state.

What parameters does get_album_tracks accept? +

get_album_tracks accepts 1 parameter: album_id. Required: album_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_album_tracks? +

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

What risk level is get_album_tracks? +

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

Can I rate-limit get_album_tracks? +

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

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

get_album_tracks is provided by the Mcp Theaudiodb MCP server (https://gateway.pipeworx.io/theaudiodb/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.