Create a new locator/cue point.
AI agents use create_locator to create or update resources in Ableton — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ableton environment.
This tool creates new metadata (locators/cue points) within an Ableton Live session. This is reversible—locators can be deleted or modified. It does not execute arbitrary code, delete data irreversibly, move money, or have severe blast radius. The impact is limited to adding organizational markers within a music project, making it a straightforward Write operation with low severity.
From the tool's definition Tool creates a new locator/cue point in Ableton Live. The verb 'create' and the description 'Create a new locator' indicate data creation. Locators are metadata markers within a session that organize playback positions.
Documented attack patterns abuse exactly the kind of access create_locator 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 create_locator:
{
"version": "1",
"default": "deny",
"tools": {
"create_locator": {
"limits": [
{
"counter": "create_locator_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_locator stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new locator/cue point. It is categorised as a Write tool in the Ableton MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ableton MCP server in PolicyLayer and add a rule for create_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.
create_locator is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
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.