Set the volume of a track in decibels.
AI agents use set_track_volume to create or update resources in Reaper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reaper environment.
This tool modifies track state (volume level) but is reversible—the change can be undone by setting a different volume value. It does not execute arbitrary code, delete data, or create financial obligations. It falls squarely into Write category. Severity is low because misuse results in audio level changes that are easily corrected with no lasting harm or data loss.
From the tool's definition Tool name 'set_track_volume' and description 'Set the volume of a track in decibels' indicate modification of track parameters in REAPER DAW. The verb 'set' and action of adjusting volume levels constitute data modification.
Documented attack patterns abuse exactly the kind of access set_track_volume gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for set_track_volume:
{
"version": "1",
"default": "deny",
"tools": {
"set_track_volume": {
"limits": [
{
"counter": "set_track_volume_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Set the volume of a track in decibels. It is categorised as a Write tool in the Reaper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 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 Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reaper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.