set_segment_continuation
Make a segment's image render as a continuation of an EARLIER segment's frame (same composition evolving — the storyboard's continues_from_segment, settable after the fact). continues_from is that earlier segment's number; pass 0 to clear the link. Regenerate the segment's image afterwards — the ...
This record as markdown: /tools/com-framesail-framesail/set-segment-continuation.md
What set_segment_continuation does on Framesail
AI agents use set_segment_continuation 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 |
continues_from | integer | — | 1-based number of the EARLIER segment whose frame this one continues; pass 0 to clear the link |
segment_number | integer | Yes | 1-based number of the segment whose image should continue an earlier frame, as reported by get_segments |
Parameters from the server's own tool schema.
Why set_segment_continuation is rated Medium
The tool creates or modifies data (the 'continues_from_segment' reference) in a reversible manner. The user can change the link or pass 0 to clear it, making this a Write action rather than Destructive. Severity is medium because modifying storyboard composition relationships could degrade video output quality if misused, but the effects are easily corrected by adjusting the reference again.
From the tool's definition Tool modifies a segment's 'continues_from_segment' property 'settable after the fact', establishing a reference link between segments.
Attacks that exploit this kind of access
The rule that runs set_segment_continuation 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 set_segment_continuation, this is the rule to start with:
set_segment_continuation 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 set_segment_continuation call is checked against it from then on.
Questions about set_segment_continuation
Make a segment's image render as a continuation of an EARLIER segment's frame (same composition evolving — the storyboard's continues_from_segment, settable after the fact). continues_from is that earlier segment's number; pass 0 to clear the link. Regenerate the segment's image afterwards — the reference is applied at generation time. 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.
set_segment_continuation accepts 3 parameters: project_id, continues_from, 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 set_segment_continuation: 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.
set_segment_continuation 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 set_segment_continuation 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 set_segment_continuation. 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.
set_segment_continuation 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