Critical Risk →

delete_track

Delete a track from the Ableton session. Parameters: - track_index: Track number (1-based). Use 0 to resolve by name instead. - track_name: Track name (alternative to track_index). If both are given, track_index takes priority.

How to control delete_track ↓

AI agents call delete_track to permanently remove resources in Ableton MCP Extended — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes a track from an Ableton Live session. Deletion cannot be undone through the tool itself (though undo may be available in the DAW). The action destroys all content associated with that track (clips, automation, device chains, etc.) and represents a clear destructive operation.

From the tool's definition Tool name is 'delete_track' with description 'Delete a track from the Ableton session.' The parameters allow specifying a track by index or name for deletion.

Documented attack patterns abuse exactly the kind of access delete_track gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Ableton MCP Extended, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_track:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_track"
  ]
}

delete_track disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Ableton MCP Extended — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the delete_track tool do? +

Delete a track from the Ableton session. Parameters: - track_index: Track number (1-based). Use 0 to resolve by name instead. - track_name: Track name (alternative to track_index). If both are given, track_index takes priority. It is categorised as a Destructive tool in the Ableton MCP Extended MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_track? +

Register the Ableton MCP Extended MCP server in PolicyLayer and add a rule for delete_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 Ableton MCP Extended. Nothing to install.

What risk level is delete_track? +

delete_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_track? +

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

How do I block delete_track completely? +

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

What MCP server provides delete_track? +

delete_track is provided by the Ableton MCP Extended MCP server (uisato/ableton-mcp-extended). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ableton MCP Extended tool call.

Deterministic rules across all 46 Ableton MCP Extended tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

46 Ableton MCP Extended tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.