Create a new MIDI or audio track at an optional index. Use when the user explicitly wants another track. NOT idempotent: every call creates a track; returns the created track and verifies that its type matches the request.
AI agents use track_create to create or update resources in Ableton Mind — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ableton Mind environment.
The tool creates new tracks in Ableton Live, modifying the session structure. This is a Write operation because it creates data reversibly—tracks can be undone or deleted. It is not Destructive (no irreversible deletion), Execute (doesn't run arbitrary code), or Financial. The medium severity reflects that misuse could clutter a session, but the effects are easily reversible.
From the tool's definition Tool description explicitly states 'Create a new MIDI or audio track' and 'every call creates a track'. This is data creation with reversible effects (tracks can be deleted).
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Create a new MIDI or audio track at an optional index. Use when the user explicitly wants another track. NOT idempotent: every call creates a track; returns the created track and verifies that its type matches the request. It is categorised as a Write tool in the Ableton Mind MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ableton Mind MCP server in PolicyLayer and add a rule for track_create: 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 Ableton Mind. Nothing to install.
track_create 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 track_create 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 track_create. 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.
track_create is provided by the Ableton Mind MCP server (ableton-mind). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →