track_list

Read-only list of regular, return, and master tracks in the current Live set. Use before addressing tracks by index or deciding where to create content; returns counts and optional return/master sections without mutating the session.

Server Ableton Mind ableton-mind
Category Read
Risk class Low
Parameters 00 required

What track_list does on Ableton Mind

AI agents call track_list to retrieve information from Ableton Mind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why track_list needs a policy

This tool retrieves and queries the structure of tracks in an Ableton Live set without creating, modifying, deleting, or executing any operations. It is purely informational and supports other tools by providing necessary context (e.g., track indices). The explicit 'read-only' designation and emphasis on non-mutation confirm it has no side effects, placing it in the Read category with low severity.

From the tool's definition Tool description explicitly states 'Read-only list' and 'without mutating the session'. It returns information about tracks (counts and sections) with no side effects.

Questions about track_list

What does the track_list tool do? +

Read-only list of regular, return, and master tracks in the current Live set. Use before addressing tracks by index or deciding where to create content; returns counts and optional return/master sections without mutating the session. It is categorised as a Read tool in the Ableton Mind MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on track_list? +

Register the Ableton Mind MCP server in PolicyLayer and add a rule for track_list: 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.

What risk level is track_list? +

track_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit track_list? +

Yes. Add a rate_limit block to the track_list 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.

How do I block track_list completely? +

Set action: deny in the PolicyLayer policy for track_list. 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.

What MCP server provides track_list? +

track_list 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.