move_item
Move one clip with optional deterministic snapping and overlap validation.
This record as markdown: /tools/cutpilot/move-item.md
What move_item does on Cutpilot
AI agents use move_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 move_item is rated Medium
Moving a clip within a timeline modifies project state reversibly—the original clip data remains intact and the operation can be undone. This is characteristic of Write operations. Severity is medium because incorrect positioning could impact edit quality and require correction, but changes are easily reversible within the editing application.
From the tool's definition Tool name 'move_item' and description 'Move one clip' indicates modification of clip position/timing within a video timeline. The context of a video editing engine confirms this is a reversible data modification operation (repositioning rather than deletion).
Attacks that exploit this kind of access
The rule that runs move_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 move_item, this is the rule to start with:
move_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 move_item call is checked against it from then on.
Questions about move_item
Move one clip with optional deterministic snapping and overlap validation. 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 move_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.
move_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 move_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 move_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.
move_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