add_music_track
Add background music to the project from the audio library (find track ids with browse_audio_library, category="music"). Defaults loop the track under the whole video at bed level (volume 0.12 ≈ -18.4 dB under narration — don't raise it without being asked); re-run export_video to hear it.
This record as markdown: /tools/com-framesail-framesail/add-music-track.md
What add_music_track does on Framesail
AI agents use add_music_track to create or update resources in Framesail, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Framesail environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
loop | boolean | — | True loops the track under the whole video; false plays it once |
name | string | — | Display name for the track on the project's timeline |
volume | number | — | Playback volume 0-1; the 0.12 default sits at bed level under narration — don't raise it unless asked |
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
start_frame | integer | — | Timeline frame at which the track starts (0 = start of the video) |
library_track_id | string | Yes | Audio library track ID, from browse_audio_library(category="music") |
Parameters from the server's own tool schema.
Why add_music_track is rated Medium
An AI agent can call add_music_track faster than any human can review: one bad instruction and it creates or modifies resources in Framesail by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_music_track 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 add_music_track, this is the rule to start with:
add_music_track stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_music_track call is checked against it from then on.
Questions about add_music_track
Add background music to the project from the audio library (find track ids with browse_audio_library, category="music"). Defaults loop the track under the whole video at bed level (volume 0.12 ≈ -18.4 dB under narration — don't raise it without being asked); re-run export_video to hear it. It is categorised as a Write tool in the Framesail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_music_track accepts 6 parameters: loop, name, volume, project_id, start_frame, library_track_id. Required: project_id, library_track_id. 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 add_music_track: 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.
add_music_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_music_track 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 add_music_track. 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.
add_music_track 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