This record as markdown: /tools/io-github-dreamrec-livepilot/get-arrangement-clips.md
What get_arrangement_clips does on Livepilot
AI agents call get_arrangement_clips to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_arrangement_clips is rated Low
This tool queries and retrieves clip information from an Ableton Live arrangement. The verb 'get' and lack of any modification language ('create', 'update', 'delete') confirm this is a read-only operation. The blast radius is minimal—an AI agent cannot cause harm by retrieving arrangement clip data.
From the tool's definition Tool name 'get_arrangement_clips' and description 'Get all arrangement clips on a track' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_arrangement_clips 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 get_arrangement_clips, this is the rule to start with:
get_arrangement_clips is read-only, so it stays allowed. 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 get_arrangement_clips call is checked against it from then on.
Questions about get_arrangement_clips
Get all arrangement clips on a track. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_arrangement_clips: 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.
get_arrangement_clips is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_arrangement_clips 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 get_arrangement_clips. 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.
get_arrangement_clips 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