add_segment_sfx
Attach a sound effect from the audio library to a segment (find track ids via browse_audio_library with category="sfx"). Re-run build_scenes to get it onto the timeline.
This record as markdown: /tools/com-framesail-framesail/add-segment-sfx.md
What add_segment_sfx does on Framesail
AI agents use add_segment_sfx 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 |
|---|---|---|---|
project_id | string | Yes | Project ID, as returned by create_project or list_projects |
segment_number | integer | Yes | 1-based segment number, as reported by get_segments |
library_track_id | string | Yes | Audio library track ID, from browse_audio_library(category="sfx") |
Parameters from the server's own tool schema.
Why add_segment_sfx is rated Medium
This tool creates or modifies video project data by attaching sound effects to segments. While it modifies the video composition, the changes are reversible (effects can be removed/changed and rebuild_scenes reapplied). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool 'adds' (modifies) sound effects to segments and requires re-running build_scenes to apply changes. Description explicitly states 'Attach a sound effect from the audio library to a segment', indicating creation/modification of video composition data.
Attacks that exploit this kind of access
The rule that runs add_segment_sfx 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_segment_sfx, this is the rule to start with:
add_segment_sfx 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_segment_sfx call is checked against it from then on.
Questions about add_segment_sfx
Attach a sound effect from the audio library to a segment (find track ids via browse_audio_library with category="sfx"). Re-run build_scenes to get it onto the timeline. 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_segment_sfx accepts 3 parameters: project_id, segment_number, library_track_id. Required: project_id, segment_number, 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_segment_sfx: 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_segment_sfx 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_segment_sfx 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_segment_sfx. 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_segment_sfx 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