duplicate_track
Duplicate a track (copies all clips, devices, and settings).
This record as markdown: /tools/io-github-dreamrec-livepilot/duplicate-track.md
What duplicate_track does on Livepilot
AI agents use duplicate_track to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why duplicate_track is rated Medium
Duplicating a track creates a new copy of an existing track with all its contents. This is a reversible write operation — the duplicate can be deleted afterward. It does not destroy original data, execute arbitrary code, or involve financial transactions. The blast radius is medium since it could clutter a project with unintended duplicates, but nothing is irreversibly lost.
From the tool's definition Duplicate a track (copies all clips, devices, and settings)
Attacks that exploit this kind of access
The rule that runs duplicate_track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For duplicate_track, this is the rule to start with:
duplicate_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 Livepilot, apply this rule, and every duplicate_track call is checked against it from then on.
Questions about duplicate_track
Duplicate a track (copies all clips, devices, and settings). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for duplicate_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 Livepilot. Nothing to install.
duplicate_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 duplicate_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 duplicate_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.
duplicate_track is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue