combine_segments
Merge a segment with an adjacent one (segment numbers must be neighbors). keep: "this" | "other" — whose creative data survives. Later segments renumber — re-check get_segments before further edits.
This record as markdown: /tools/com-framesail-framesail/combine-segments.md
What combine_segments does on Framesail
AI agents use combine_segments 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 |
|---|---|---|---|
keep | string | — | Whose creative data survives the merge: "this" (segment_number) or "other" (with_segment_number) |
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 |
with_segment_number | integer | Yes | 1-based number of the adjacent segment to merge with (must neighbor segment_number) |
Parameters from the server's own tool schema.
Why combine_segments is rated Medium
This is a reversible modification operation that alters video project data (segment consolidation and renumbering). It does not delete segments irreversibly (both exist before merge, one is incorporated into the other), nor does it execute arbitrary code or have financial impact.
From the tool's definition Tool 'combine_segments' merges two adjacent segments, modifying the project structure. Description explicitly states 'whose creative data survives,' indicating selective data retention and modification. Segments are renumbered, affecting project state.
Attacks that exploit this kind of access
The rule that runs combine_segments 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 combine_segments, this is the rule to start with:
combine_segments 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 combine_segments call is checked against it from then on.
Questions about combine_segments
Merge a segment with an adjacent one (segment numbers must be neighbors). keep: "this" | "other" — whose creative data survives. Later segments renumber — re-check get_segments before further edits. 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.
combine_segments accepts 4 parameters: keep, project_id, segment_number, with_segment_number. Required: project_id, segment_number, with_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 combine_segments: 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.
combine_segments 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 combine_segments 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 combine_segments. 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.
combine_segments 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