Delete a cue point at a position. Parameters: - bar: Bar number (1-based). - beat: Beat position (0-based).
AI agents call delete_cue_point 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.
Cue points in Ableton Live are navigation markers that organize session structure. Deleting them irreversibly removes these markers. While less critical than deleting tracks or clips containing audio data, cue point deletion cannot be undone and represents permanent loss of session organization metadata.
From the tool's definition Tool name 'delete_cue_point' and description 'Delete a cue point at a position' explicitly perform deletion. The sibling tools include 'delete_arrangement_clip', 'delete_device', and 'delete_track', confirming this server exposes destructive operations.
Documented attack patterns abuse exactly the kind of access delete_cue_point 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_cue_point:
{
"version": "1",
"default": "deny",
"hide": [
"delete_cue_point"
]
}delete_cue_point 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 cue point at a position. Parameters: - bar: Bar number (1-based). - beat: Beat position (0-based). 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.
Register the Ableton MCP Extended MCP server in PolicyLayer and add a rule for delete_cue_point: 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.
delete_cue_point 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_cue_point 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_cue_point. 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_cue_point 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.
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.