クリップを別のスロットに複製
AI agents use duplicate_clip 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 a new copy of an audio/MIDI clip in Ableton Live, which is a reversible write operation. It modifies the arrangement by adding content but does not delete, execute arbitrary code, or cause financial transactions. The severity is medium because misuse could result in unintended duplication of clips, requiring manual cleanup, but the effect is fully reversible and confined to the music project.
From the tool's definition Tool name 'duplicate_clip' indicates copying/replication of a clip to another slot. The Japanese description 'クリップを別のスロットに複製' translates to 'duplicate/copy a clip to another slot', confirming non-destructive modification of the arrangement.
Attacks that exploit this kind of access
クリップを別のスロットに複製. 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 duplicate_clip: 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.
duplicate_clip 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 duplicate_clip 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 duplicate_clip. 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.
duplicate_clip 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 →