browse_audio_library
Browse the audio library for background music and sound effects. category: "music" | "sfx". Returns track ids for add_music_track / add_segment_sfx.
This record as markdown: /tools/com-framesail-framesail/browse-audio-library.md
What browse_audio_library does on Framesail
AI agents call browse_audio_library to retrieve information from Framesail 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 |
|---|---|---|---|
mood | string | — | Filter by the track's mood tag; empty for no filter |
genre | string | — | Filter by the track's genre tag; empty for no filter |
search | string | — | Free-text search over track names/descriptions; empty for no filter |
category | string | — | Track kind: "music" (background tracks) or "sfx" (sound effects); empty returns both |
Parameters from the server's own tool schema.
Why browse_audio_library is rated Low
This is a query/search operation that lists or returns metadata (track IDs) from an existing audio library. It has no side effects, does not create or modify data, and does not execute code or trigger external operations. The primary use is to discover and retrieve identifiers for use by other tools (add_music_track, add_segment_sfx), making it a classic Read operation with minimal risk.
From the tool's definition Tool description states 'Browse the audio library' and 'Returns track ids' — it retrieves data from a music/sound effects library without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
The rule that runs browse_audio_library safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Framesail, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_audio_library, this is the rule to start with:
browse_audio_library 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 Framesail, apply this rule, and every browse_audio_library call is checked against it from then on.
Questions about browse_audio_library
Browse the audio library for background music and sound effects. category: "music" | "sfx". Returns track ids for add_music_track / add_segment_sfx. It is categorised as a Read tool in the Framesail MCP Server, which means it retrieves data without modifying state.
browse_audio_library accepts 4 parameters: mood, genre, search, category. The full parameter table on this page comes from the server's own tool schema.
Register the Framesail MCP server in PolicyLayer and add a rule for browse_audio_library: 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 Framesail. Nothing to install.
browse_audio_library 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 browse_audio_library 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 browse_audio_library. 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.
browse_audio_library is provided by the Framesail MCP server (https://api.framesail.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Framesail, and thousands of servers like it.
This server
Across the catalogue