create_clip
Create an empty MIDI clip in a clip slot (length in beats).
This record as markdown: /tools/io-github-dreamrec-livepilot/create-clip.md
What create_clip does on Livepilot
AI agents use create_clip to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why create_clip is rated Medium
This tool creates new MIDI clip objects in Ableton Live's session or arrangement. Creation of media assets is a Write-category operation: it modifies the project state but is reversible (clips can be deleted). The blast radius is medium because an AI agent could clutter a project with many clips or create clips at unintended times, disrupting workflow, but the damage is not permanent or financial.
From the tool's definition Tool description states 'Create an empty MIDI clip' — the verb 'create' and the action of adding a new clip to a project are characteristic of Write operations that modify project state reversibly.
Attacks that exploit this kind of access
The rule that runs create_clip safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_clip, this is the rule to start with:
create_clip 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every create_clip call is checked against it from then on.
Questions about create_clip
Create an empty MIDI clip in a clip slot (length in beats). It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for create_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 Livepilot. Nothing to install.
create_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 create_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 create_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.
create_clip is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue