This record as markdown: /tools/io-github-dreamrec-livepilot/create-midi-track.md
What create_midi_track does on Livepilot
AI agents use create_midi_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_midi_track is rated Medium
Creating a MIDI track modifies the project state by adding a new track object, which is a Write operation. The effect is reversible (the track can be deleted). Severity is medium because while it modifies the session, it does not execute arbitrary code, trigger external operations, delete data, or move money.
From the tool's definition Tool name 'create_midi_track' indicates creation of a new MIDI track in Ableton Live 12. The description is empty, but the name and context within a music production copilot clearly indicates reversible creation of a track/data structure.
Attacks that exploit this kind of access
The rule that runs create_midi_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_midi_track, this is the rule to start with:
create_midi_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_midi_track call is checked against it from then on.
Questions about create_midi_track
create_midi_track is a write tool on the Livepilot MCP server. 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_midi_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_midi_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_midi_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_midi_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_midi_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