change_segment_type

Change a segment's visual type: "image" | "video" | "overlay_scene". carry_frame=true reuses the already-rendered image as the video start frame (or vice versa) instead of recreating it.

SERVERFramesail SOURCEhttps://api.framesail.com/mcp

Medium RISK CLASS

Category Write

Parameters 43 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-framesail-framesail/change-segment-type.md

WHAT IT DOES

What change_segment_type does on Framesail

AI agents use change_segment_type 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
`carry_frame`	boolean	—	True reuses the already-rendered frame as the new type's starting visual instead of recreating it from scratch
`segment_type`	string	Yes	New visual type: "image", "video", or "overlay_scene"
`segment_number`	integer	Yes	1-based segment number, as reported by get_segments

Parameters from the server's own tool schema.

RISK

Why change_segment_type is rated Medium

This tool creates or modifies video segment metadata and properties reversibly. It changes the type attribute of a segment and optionally carries forward rendered frames, which are metadata/state modifications rather than destructive deletions. The changes can be undone by reverting to a previous segment type.

From the tool's definition Tool modifies segment properties by changing visual type ('image' | 'video' | 'overlay_scene'), which alters the structure and composition of video content. The carry_frame parameter controls how existing rendered assets are reused during the modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs change_segment_type 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 change_segment_type, this is the rule to start with:

change_segment_type Rate-limited

change_segment_type 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change_segment_type": {
      "limits": [
        {
          "counter": "change_segment_type_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Framesail, apply this rule, and every change_segment_type call is checked against it from then on.

FAQ

Questions about change_segment_type

What does the change_segment_type tool do? +

Change a segment's visual type: "image" | "video" | "overlay_scene". carry_frame=true reuses the already-rendered image as the video start frame (or vice versa) instead of recreating it. 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.

What parameters does change_segment_type accept? +

change_segment_type accepts 4 parameters: project_id, carry_frame, segment_type, segment_number. Required: project_id, segment_type, segment_number. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on change_segment_type? +

Register the Framesail MCP server in PolicyLayer and add a rule for change_segment_type: 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.

What risk level is change_segment_type? +

change_segment_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit change_segment_type? +

Yes. Add a rate_limit block to the change_segment_type 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.

How do I block change_segment_type completely? +

Set action: deny in the PolicyLayer policy for change_segment_type. 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.

What MCP server provides change_segment_type? +

change_segment_type 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.

KEEP EXPLORING

More on Framesail, and thousands of servers like it.

This server

All 68 Framesail tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →