delete_locator

THE RISK

Critical Risk

Why delete_locator needs a policy

Locators are markers within an Ableton Live session that represent important positions/sections. Deletion is irreversible and cannot be undone programmatically through this tool.

From the tool's definition Tool name is 'delete_locator' with description 'Delete a locator.' The verb 'delete' indicates irreversible removal of data (a locator marker in Ableton Live session).

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

POLICY

How to control delete_locator

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_locator:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_locator"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ableton tools

Destructive clear_clip_automation Clear automation for a clip parameter. Destructive delete_clip Delete a clip from a clip slot. Destructive delete_device Delete a device from a track. Destructive delete_scene Delete a scene. Destructive delete_track Delete a track. Destructive delete_warp_marker Delete a warp marker from an audio clip. Destructive remove_all_notes Remove all notes from a clip. Destructive remove_notes remove_notes

All 128 Ableton tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Ableton → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_locator

What does the delete_locator tool do? +

Delete a locator. 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.

How do I enforce a policy on delete_locator? +

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

What risk level is delete_locator? +

delete_locator 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_locator? +

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

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

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

Enforce policy on every Ableton tool call.

Start from Ableton, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →