razor_all_tracks
Split every unlocked item crossing an absolute timeline time.
This record as markdown: /tools/cutpilot/razor-all-tracks.md
What razor_all_tracks does on Cutpilot
AI agents invoke razor_all_tracks to trigger actions in Cutpilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why razor_all_tracks is rated High
This tool performs a destructive-style edit operation (splitting/razoring all items across every unlocked track at a given time) that modifies the timeline state. However, in non-linear video editing, splits can typically be undone, making this a reversible modification rather than truly irreversible.
From the tool's definition Split every unlocked item crossing an absolute timeline time
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs razor_all_tracks 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 razor_all_tracks, this is the rule to start with:
razor_all_tracks stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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 razor_all_tracks call is checked against it from then on.
Questions about razor_all_tracks
Split every unlocked item crossing an absolute timeline time. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Cutpilot MCP server in PolicyLayer and add a rule for razor_all_tracks: 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.
razor_all_tracks is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the razor_all_tracks 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 razor_all_tracks. 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.
razor_all_tracks 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.
Across the catalogue