Makes the loop twice as long and duplicates notes and envelopes. Duplicates the clip start/end range if the clip is not looped.
AI agents invoke duplicate_clip_loop to trigger actions in Ableton Copilot MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
duplicate_clip_loop triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
Makes the loop twice as long and duplicates notes and envelopes. Duplicates the clip start/end range if the clip is not looped. It is categorised as a Execute tool in the Ableton Copilot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ableton Copilot MCP server in PolicyLayer and add a rule for duplicate_clip_loop: 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 Copilot MCP. Nothing to install.
duplicate_clip_loop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the duplicate_clip_loop 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_loop. 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_loop is provided by the Ableton Copilot MCP server (xiaolaa2/ableton-copilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.