set_track_volume
Set a track's volume (0.0-1.0). Use negative track_index for return tracks (-1=A, -2=B).
This record as markdown: /tools/io-github-dreamrec-livepilot/set-track-volume.md
What set_track_volume does on Livepilot
AI agents use set_track_volume 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_track_volume is rated Medium
This tool creates or modifies data reversibly—the volume can be adjusted up or down without permanent loss or destruction. It affects audio mixing state but does not execute external code, delete data, or move money. The moderate severity reflects that incorrect volume settings in a live DAW could cause audio issues or disrupt a performance, but the effect is fully reversible and limited to a single parameter.
From the tool's definition 'Set a track's volume (0.0-1.0)' describes modifying audio parameters; this is a reversible state change to a track's mixer properties.
Attacks that exploit this kind of access
The rule that runs set_track_volume 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_track_volume, this is the rule to start with:
set_track_volume 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_track_volume call is checked against it from then on.
Questions about set_track_volume
Set a track's volume (0.0-1.0). Use negative track_index for return tracks (-1=A, -2=B). 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_track_volume: 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_track_volume 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_track_volume 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_track_volume. 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_track_volume 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