remove_music_track
Remove a music track from the project.
This record as markdown: /tools/com-framesail-framesail/remove-music-track.md
What remove_music_track does on Framesail
AI agents call remove_music_track to permanently remove resources in Framesail, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
track_id | string | Yes | ID of the music track to remove, from list_music_tracks |
Parameters from the server's own tool schema.
Why remove_music_track is rated Critical
Removing a music track is an irreversible deletion of a project asset. Unlike updating or toggling, 'remove' implies the track is eliminated from the project without a stated undo mechanism, placing it in the Destructive category. Severity is medium since it affects a single audio asset within a video project rather than the entire project.
From the tool's definition "Remove a music track from the project"
Attacks that exploit this kind of access
The rule that runs remove_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 remove_music_track, this is the rule to start with:
remove_music_track is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every remove_music_track call is checked against it from then on.
Questions about remove_music_track
Remove a music track from the project. It is categorised as a Destructive tool in the Framesail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_music_track accepts 1 parameter: track_id. Required: 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 remove_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.
remove_music_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.
Across the catalogue