AI agents use send_set_volume to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
This tool modifies mixing parameters (send volume) in a reversible manner—the user can adjust the volume again to different values. It does not execute arbitrary code, delete data, or move money. It falls under Write category as it creates or modifies data (audio routing/mixing state) reversibly.
From the tool's definition Tool name 'send_set_volume' indicates modification of a send volume parameter in REAPER's mixing context. The verb 'set' combined with 'volume' describes a state change operation that modifies audio routing levels.
Documented attack patterns abuse exactly the kind of access send_set_volume gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for send_set_volume:
{
"version": "1",
"default": "deny",
"tools": {
"send_set_volume": {
"limits": [
{
"counter": "send_set_volume_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_set_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 send volume. It is categorised as a Write tool in the ReaperMCP 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 send_set_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 ReaperMCP. Nothing to install.
send_set_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 send_set_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 send_set_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.
send_set_volume is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, 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.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.