This record as markdown: /tools/io-github-dreamrec-livepilot/set-clip-pitch.md
What set_clip_pitch does on Livepilot
AI agents use set_clip_pitch 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 set_clip_pitch is rated Medium
The 'set_clip_pitch' tool modifies clip properties (pitch) within Ableton Live, which is a reversible change to project data. This qualifies as Write rather than Execute, as it updates a specific parameter rather than executing arbitrary code or running queries. However, without a description, confidence is moderate.
From the tool's definition Tool name 'set_clip_pitch' indicates modification of audio clip pitch properties in Ableton Live. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
The rule that runs set_clip_pitch 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 set_clip_pitch, this is the rule to start with:
set_clip_pitch 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 set_clip_pitch call is checked against it from then on.
Questions about set_clip_pitch
set_clip_pitch is a write tool on the Livepilot MCP server. 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 set_clip_pitch: 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.
set_clip_pitch 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 set_clip_pitch 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 set_clip_pitch. 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.
set_clip_pitch 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