regenerate_segment_asset
Regenerate a segment's primary image or video with optional overrides — the API equivalent of the editor's expert drawer. asset_type: "image" | "video" (for a video segment, "image" targets its start frame). Use a different model, override prompt sections (see get_section_template("segment_image"...
This record as markdown: /tools/com-framesail-framesail/regenerate-segment-asset.md
What regenerate_segment_asset does on Framesail
AI agents invoke regenerate_segment_asset to trigger actions in Framesail. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | — | Model ID to render with; empty uses the job's default (see list_models("segment_image") / list_models("segment_video")) |
settings | object | — | Model-specific settings (e.g. image quality, video duration); valid keys come from the model's settings_schema in list_models |
asset_type | string | Yes | "image" or "video"; for a video segment, "image" targets its start frame |
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 |
editable_sections | object | — | Per-call prompt section overrides, keyed by section name; see get_section_template("segment_image") or ("segment_video") |
Parameters from the server's own tool schema.
Why regenerate_segment_asset is rated High
This tool executes code/external operations (image/video generation via ML models with configurable parameters). While it modifies a video project, it is not irreversible deletion (not Destructive) and not a financial transaction (not Financial).
From the tool's definition The tool 'regenerates' segment assets (image or video) with 'optional overrides' and 'different model' choices, allowing the caller to modify prompts and settings, then 're-run' the asset generation.
Attacks that exploit this kind of access
The rule that runs regenerate_segment_asset 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 regenerate_segment_asset, this is the rule to start with:
regenerate_segment_asset stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 regenerate_segment_asset call is checked against it from then on.
Questions about regenerate_segment_asset
Regenerate a segment's primary image or video with optional overrides — the API equivalent of the editor's expert drawer. asset_type: "image" | "video" (for a video segment, "image" targets its start frame). Use a different model, override prompt sections (see get_section_template("segment_image")), or tweak settings (e.g. image quality), then re-run just this asset. Async — returns {job_id}. It is categorised as a Execute tool in the Framesail MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
regenerate_segment_asset accepts 6 parameters: model, settings, asset_type, project_id, segment_number, editable_sections. Required: asset_type, 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 regenerate_segment_asset: 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.
regenerate_segment_asset is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the regenerate_segment_asset 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 regenerate_segment_asset. 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.
regenerate_segment_asset 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