AI agents call delete_track to permanently remove resources in Ableton — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a track in a music production session irreversibly removes the track and all associated clips, automation, and settings. This action cannot be undone through the MCP tool itself and represents permanent loss of data. This places it in the Destructive category (more severe than Execute or Write).
From the tool's definition Tool name is 'delete_track' and description states 'Delete a track.' The verb 'delete' and action of removing a track from an Ableton Live session represent irreversible data destruction.
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, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_track:
{
"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.
Free to start. No card required.
Delete a track. It is categorised as a Destructive tool in the Ableton MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Ableton 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. Nothing to install.
delete_track is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
delete_track is provided by the Ableton MCP server (jpoindexter/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ableton, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
128 Ableton tools catalogued and risk-classified — across an index of 43,000+ MCP servers.