This record as markdown: /tools/io-github-dreamrec-livepilot/create-return-track.md
What create_return_track does on Livepilot
AI agents use create_return_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 create_return_track is rated Medium
This tool creates a new audio/MIDI return track in Ableton Live, which modifies the project by adding a new track. This is a Write operation because it creates new data structures that can be deleted or undone. It is not Execute because it does not run arbitrary code or trigger external operations based on user input parameters.
From the tool's definition Tool name 'create_return_track' and description 'Create a new return track' indicate creation of a new track object in Ableton Live. The verb 'create' and the action of adding a new track are reversible modifications to the project structure.
Attacks that exploit this kind of access
The rule that runs create_return_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 create_return_track, this is the rule to start with:
create_return_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 create_return_track call is checked against it from then on.
Questions about create_return_track
Create a new return track. 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 create_return_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.
create_return_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 create_return_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 create_return_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.
create_return_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