place_asset_on_timeline
Place a local source range onto a compatible target track by appending, ripple-inserting across all tracks, or overwriting only the target range with source-continuous remainder clips.
This record as markdown: /tools/cutpilot/place-asset-on-timeline.md
What place_asset_on_timeline does on Cutpilot
AI agents use place_asset_on_timeline 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 place_asset_on_timeline is rated Medium
This tool creates or modifies video timeline data (edits) in a reversible manner—clips can be removed, repositioned, or undone in a typical video editor. It does not execute arbitrary code, delete irreversibly, or trigger financial transactions. The 'overwriting' aspect is local to the target track range and does not constitute permanent data destruction since edits are typically undoable in video software.
From the tool's definition Tool description states it can 'Place a local source range onto a compatible target track by appending, ripple-inserting across all tracks, or overwriting'.
Attacks that exploit this kind of access
The rule that runs place_asset_on_timeline 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 place_asset_on_timeline, this is the rule to start with:
place_asset_on_timeline 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 place_asset_on_timeline call is checked against it from then on.
Questions about place_asset_on_timeline
Place a local source range onto a compatible target track by appending, ripple-inserting across all tracks, or overwriting only the target range with source-continuous remainder clips. 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 place_asset_on_timeline: 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.
place_asset_on_timeline 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 place_asset_on_timeline 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 place_asset_on_timeline. 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.
place_asset_on_timeline 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