flatten_track
Flatten a frozen track — commit rendered audio permanently.
This record as markdown: /tools/io-github-dreamrec-livepilot/flatten-track.md
What flatten_track does on Livepilot
AI agents call flatten_track to permanently remove resources in Livepilot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why flatten_track is rated Critical
Flattening a track permanently overwrites/removes the original multi-layer track data, replacing it with a static audio file. This is irreversible — the original arrangement, automation, and individual track elements cannot be recovered without undo (which is session-state dependent and not guaranteed in an AI agent context). While not a literal delete, it destroys the editable state of data.
From the tool's definition Tool description states 'commit rendered audio permanently' — this is irreversible data transformation. 'Flatten' in audio production means consolidating multiple layers into a single audio file, destroying the original track structure and individual layer…
Attacks that exploit this kind of access
The rule that runs flatten_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 flatten_track, this is the rule to start with:
flatten_track is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every flatten_track call is checked against it from then on.
Questions about flatten_track
Flatten a frozen track — commit rendered audio permanently. It is categorised as a Destructive tool in the Livepilot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Livepilot MCP server in PolicyLayer and add a rule for flatten_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.
flatten_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the flatten_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 flatten_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.
flatten_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.
Across the catalogue