remove_segment_sfx
Remove a sound effect from a segment. With one SFX attached, no name needed; with several, pass sfx_name (the asset name shown by get_segment_assets).
This record as markdown: /tools/com-framesail-framesail/remove-segment-sfx.md
What remove_segment_sfx does on Framesail
AI agents use remove_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 |
|---|---|---|---|
sfx_name | string | — | Name of the SFX asset to remove, as shown by get_segment_assets; needed only when the segment has several SFX attached |
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 |
Parameters from the server's own tool schema.
Why remove_segment_sfx is rated Medium
Removing a sound effect is a reversible modification to a segment's assets — it detaches/unlinks the SFX but does not permanently destroy the underlying audio asset. The tool modifies project data (Write), and since the asset itself is not purged, it is not Destructive. Misuse could disrupt a video project's audio configuration, hence medium severity.
From the tool's definition Remove a sound effect from a segment
Attacks that exploit this kind of access
The rule that runs remove_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 remove_segment_sfx, this is the rule to start with:
remove_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 remove_segment_sfx call is checked against it from then on.
Questions about remove_segment_sfx
Remove a sound effect from a segment. With one SFX attached, no name needed; with several, pass sfx_name (the asset name shown by get_segment_assets). 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.
remove_segment_sfx accepts 3 parameters: sfx_name, project_id, segment_number. Required: project_id, segment_number. 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_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.
remove_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 remove_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 remove_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.
remove_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