ドラムトラックを作成。パターン: basic_beat, four_on_floor, trap, breakbeat
AI agents use create_drum_track to create or update resources in Ableton MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ableton MCP environment.
This tool creates new musical content (a drum track) within Ableton Live, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The effect is localized to track creation within a DAW session. Severity is medium because misuse could result in unwanted tracks being added to a project, but the operation is easily undoable (undo/delete track).
From the tool's definition Tool name 'create_drum_track' and description indicate creation of a new drum track with selectable patterns (basic_beat, four_on_floor, trap, breakbeat).
Attacks that exploit this kind of access
ドラムトラックを作成。パターン: basic_beat, four_on_floor, trap, breakbeat. It is categorised as a Write tool in the Ableton MCP 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_drum_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 MCP. Nothing to install.
create_drum_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_drum_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_drum_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_drum_track is provided by the Ableton MCP server (keigotak/abletonmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →