Create a send from one track to another.
AI agents use create_send 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 creates a new send (an audio routing element) which modifies the track configuration in the DAW project. This is a reversible operation—sends can be deleted or modified—so it falls under Write rather than Destructive. The severity is medium because misconfiguration could route audio unexpectedly or disrupt the mixing setup, but the effect is not irreversible and does not cause data loss or financial impact.
From the tool's definition Tool name 'create_send' and description 'Create a send from one track to another' indicate the creation of a routing connection in REAPER DAW.
Documented attack patterns abuse exactly the kind of access create_send 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 create_send:
{
"version": "1",
"default": "deny",
"tools": {
"create_send": {
"limits": [
{
"counter": "create_send_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_send 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.
Create a send from one track to another. 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 create_send: 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.
create_send 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 create_send 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 create_send. 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.
create_send 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.