Set track volume.
AI agents use set_track_volume to create or update resources in Scythe MCP REAPER — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scythe MCP REAPER environment.
Setting track volume modifies DAW state reversibly—the change can be undone by setting it to a different value. While the impact on audio output is real, the action itself is a simple parameter update characteristic of Write operations. Severity is medium because misuse could alter a music project's mix undesirably, but the action is easily recoverable and does not trigger external systems or irreversible changes.
From the tool's definition Tool name 'set_track_volume' and description 'Set track volume' indicate modification of track parameters in REAPER DAW.
Attacks that exploit this kind of access
Set track volume. It is categorised as a Write tool in the Scythe MCP REAPER MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scythe MCP REAPER 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 Scythe MCP REAPER. 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 Scythe MCP REAPER MCP server (yura9011/scythe_mcp_reaper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →