track_get_info

Read-only details for one regular track by index. Use before track-scoped edits to inspect name, type, volume, panning, sends, clip slots, clips, and device counts; returns verified state without mutating the session.

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

What track_get_info does on Ableton Mind

AI agents call track_get_info 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_get_info needs a policy

This tool performs a pure read operation with no side effects. It queries the Live Object Model to retrieve track metadata and state information, explicitly without modification. No data is created, deleted, executed, or financial value is affected. This is a straightforward Read category tool with low blast radius if misused by an AI agent.

From the tool's definition Tool name 'track_get_info' and description states it is 'Read-only details' that 'returns verified state without mutating the session.' It retrieves track information (name, type, volume, panning, sends, clip slots, clips, device counts) for inspection…

Questions about track_get_info

What does the track_get_info tool do? +

Read-only details for one regular track by index. Use before track-scoped edits to inspect name, type, volume, panning, sends, clip slots, clips, and device counts; returns verified state 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_get_info? +

Register the Ableton Mind MCP server in PolicyLayer and add a rule for track_get_info: 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_get_info? +

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

Can I rate-limit track_get_info? +

Yes. Add a rate_limit block to the track_get_info 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_get_info completely? +

Set action: deny in the PolicyLayer policy for track_get_info. 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_get_info? +

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