Cut selected items to clipboard.
AI agents use cut_selected_items 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.
Cutting items is a write operation as it modifies audio/MIDI data state reversibly. While destructive-sounding, the cut preserves data in clipboard allowing undo/redo in REAPER, making it Write rather than Destructive. Severity is medium because misuse could remove important production work, but the reversibility and typical undo/redo capabilities in DAWs mitigate the risk.
From the tool's definition Tool description states 'Cut selected items to clipboard' - this modifies the state of selected items in REAPER by removing them from their current location and placing them in the clipboard, which is a reversible operation (paste can restore them).
Documented attack patterns abuse exactly the kind of access cut_selected_items 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 cut_selected_items:
{
"version": "1",
"default": "deny",
"tools": {
"cut_selected_items": {
"limits": [
{
"counter": "cut_selected_items_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}cut_selected_items 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.
Cut selected items to clipboard. 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 cut_selected_items: 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.
cut_selected_items 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 cut_selected_items 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 cut_selected_items. 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.
cut_selected_items 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.