update_music_track
Tweak a music track. fields keys: name, volume (0-1), loop, start_frame, duration_frames, position, trim_start_frame, trim_end_frame.
This record as markdown: /tools/com-framesail-framesail/update-music-track.md
What update_music_track does on Framesail
AI agents use update_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 |
|---|---|---|---|
fields | object | Yes | Partial dict of track fields to patch; allowed keys: name, volume (0-1), loop, start_frame, duration_frames, position, trim_start_frame, trim_end_frame |
track_id | string | Yes | Music track ID, from list_music_tracks or add_music_track |
Parameters from the server's own tool schema.
Why update_music_track is rated Medium
The tool creates or modifies data (music track properties) reversibly. It adjusts parameters of an existing track rather than permanently deleting it or executing arbitrary code. The changes can be undone by updating the fields again. Severity is medium because misuse could corrupt a video project's audio composition, requiring rework, but the damage is repairable and contained to the video editing context.
From the tool's definition Tool description states 'Tweak a music track' with modifiable fields including name, volume, loop, start_frame, duration_frames, position, trim_start_frame, and trim_end_frame. These are reversible modifications to existing media assets.
Attacks that exploit this kind of access
The rule that runs update_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 update_music_track, this is the rule to start with:
update_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 update_music_track call is checked against it from then on.
Questions about update_music_track
Tweak a music track. fields keys: name, volume (0-1), loop, start_frame, duration_frames, position, trim_start_frame, trim_end_frame. 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.
update_music_track accepts 2 parameters: fields, track_id. Required: fields, 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 update_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.
update_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 update_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 update_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.
update_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