AI agents use send_remove 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 operation modifies the project state by removing a send routing, which is a Write-category action (reversible configuration change). It is not Destructive because sends can be recreated, and not Read because it changes state. Severity is medium because misuse could disrupt an audio project's mixing structure, but the change is undoable via undo or re-creation of the send.
From the tool's definition Tool name 'send_remove' and description 'Remove a send' indicate removal of an audio routing element (a send in REAPER is a track control that routes audio to auxiliary tracks).
Documented attack patterns abuse exactly the kind of access send_remove 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_remove:
{
"version": "1",
"default": "deny",
"tools": {
"send_remove": {
"limits": [
{
"counter": "send_remove_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_remove 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.
Remove a send. 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_remove: 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_remove 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_remove 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_remove. 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_remove 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.