set_send_dest_channels
AI agents use set_send_dest_channels 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.
Based on naming convention, this tool likely reconfigures send destination channels—a reversible configuration change in audio mixing. This is a Write operation (modifies audio routing state) rather than Read (no data retrieval), Execute (no code/command execution implied), or Destructive (changes are typically undoable in DAW). Severity is medium because misconfiguration could disrupt mixes but is reversible.
From the tool's definition Tool name 'set_send_dest_channels' indicates modification of audio send routing/channel assignments in REAPER DAW. The 'set_' prefix conventionally denotes state modification. Empty description reduces specificity.
Documented attack patterns abuse exactly the kind of access set_send_dest_channels 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_send_dest_channels:
{
"version": "1",
"default": "deny",
"tools": {
"set_send_dest_channels": {
"limits": [
{
"counter": "set_send_dest_channels_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_send_dest_channels 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_dest_channels. 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_send_dest_channels: 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_send_dest_channels 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_send_dest_channels 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_send_dest_channels. 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_send_dest_channels 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.