New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

split_segment

Split a segment at the given time offsets (ms, 1-3 cuts → 2-4 parts). inherit_index picks which resulting part keeps the original creative data. Later segments renumber — re-check get_segments before further edits.

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/split-segment.md

What split_segment does on Framesail

AI agents use split_segment 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.

ParameterTypeRequiredDescription
offsets_ms array Yes Cut points as millisecond offsets from the segment start, ascending; 1-3 cuts producing 2-4 parts
project_id string Yes Project ID, as returned by create_project or list_projects
inherit_index integer 0-based index of the resulting part that keeps the original creative data (default: the first part)
segment_number integer Yes 1-based number of the segment to split, as reported by get_segments

Parameters from the server's own tool schema.

Why split_segment is rated Medium

The tool creates a reversible structural modification to video segments by splitting them at specified timestamps and redistributing creative data and indices. This is a write operation because it modifies existing data structure (segment splitting and renumbering) without permanently deleting content. The change is reversible through recombination or undo.

From the tool's definition Tool description states it performs splitting operations that modify segment structure ('Split a segment at the given time offsets', 'inherit_index picks which resulting part keeps the original creative data', 'Later segments renumber').

Questions about split_segment

What does the split_segment tool do? +

Split a segment at the given time offsets (ms, 1-3 cuts → 2-4 parts). inherit_index picks which resulting part keeps the original creative data. 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.

What parameters does split_segment accept? +

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

How do I enforce a policy on split_segment? +

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

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

Can I rate-limit split_segment? +

Yes. Add a rate_limit block to the split_segment 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 split_segment completely? +

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

split_segment 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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Framesail's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.