edit_track
Configure track role, lock/mute, gain, denoise, loudness normalization, or video opacity.
This record as markdown: /tools/cutpilot/edit-track.md
What edit_track does on Cutpilot
AI agents use edit_track 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 edit_track is rated Medium
This tool modifies project state by adjusting track parameters (gain, opacity, mute state, denoise settings, loudness normalization). These changes are reversible and do not permanently delete or destroy data, placing it in the Write category. Severity is medium because misuse could render a video project unusable or require significant rework, but changes are not irreversible.
From the tool's definition Tool description states it can 'Configure track role, lock/mute, gain, denoise, loudness normalization, or video opacity' — these are modifications to track settings that alter the audio/video properties of a project but are reversible (settings can be…
Attacks that exploit this kind of access
The rule that runs edit_track 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 edit_track, this is the rule to start with:
edit_track 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 edit_track call is checked against it from then on.
Questions about edit_track
Configure track role, lock/mute, gain, denoise, loudness normalization, or video opacity. 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 edit_track: 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.
edit_track 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 edit_track 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 edit_track. 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.
edit_track 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