split_item
Split one timeline item at an absolute timeline time while preserving source continuity and redistributing fades/keyframes.
This record as markdown: /tools/cutpilot/split-item.md
What split_item does on Cutpilot
AI agents use split_item to create or update resources in Cutpilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cutpilot environment.
Why split_item is rated Medium
This tool creates new timeline segments and rearranges animation/effect keyframes, which constitutes data modification rather than mere querying (Read) or deletion (Destructive). While the operation is technically reversible through undo, it directly alters project state. It does not execute arbitrary external code or move financial resources.
From the tool's definition The tool 'split_item' modifies timeline items by splitting them at specified positions while 'redistributing fades/keyframes.' This is a reversible modification operation that changes the structure of video editing timeline data.
Attacks that exploit this kind of access
The rule that runs split_item safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For split_item, this is the rule to start with:
split_item 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 Cutpilot, apply this rule, and every split_item call is checked against it from then on.
Questions about split_item
Split one timeline item at an absolute timeline time while preserving source continuity and redistributing fades/keyframes. It is categorised as a Write tool in the Cutpilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cutpilot MCP server in PolicyLayer and add a rule for split_item: 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 Cutpilot. Nothing to install.
split_item 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 split_item 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 split_item. 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.
split_item is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cutpilot, and thousands of servers like it.
This server
Across the catalogue