Create a new MIDI track in the Ableton session.
AI agents use create_midi_track to create or update resources in AbletonMCP Enhanced — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AbletonMCP Enhanced environment.
This tool creates a new MIDI track, which modifies the state of the Ableton Live project by adding a new track. This is a Write operation because it creates new data/objects that can be undone or deleted. It is not Destructive because the action is reversible through standard undo functionality in Ableton.
From the tool's definition Tool name and description: 'Create a new MIDI track in the Ableton session.' The word 'Create' indicates a reversible write operation that adds a new object to the session.
Documented attack patterns abuse exactly the kind of access create_midi_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AbletonMCP Enhanced, and nothing reaches the server without passing your rules. This is the rule we recommend for create_midi_track:
{
"version": "1",
"default": "deny",
"tools": {
"create_midi_track": {
"limits": [
{
"counter": "create_midi_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_midi_track 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 MIDI track in the Ableton session. It is categorised as a Write tool in the AbletonMCP Enhanced MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AbletonMCP Enhanced MCP server in PolicyLayer and add a rule for create_midi_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 AbletonMCP Enhanced. Nothing to install.
create_midi_track 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_midi_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 create_midi_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.
create_midi_track is provided by the AbletonMCP Enhanced MCP server (itsuzef/ableton-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AbletonMCP Enhanced, 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.
24 AbletonMCP Enhanced tools catalogued and risk-classified — across an index of 43,000+ MCP servers.