Paste items from clipboard at edit cursor.
AI agents use paste_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.
Pasting items into a REAPER project creates or inserts new elements into the composition, which is a reversible modification of project state. This falls under Write (creates/modifies data reversibly) rather than Execute, since the action itself is deterministic insertion rather than arbitrary code execution.
From the tool's definition Tool description states 'Paste items from clipboard at edit cursor' — this modifies the DAW project by inserting content (audio/MIDI items) into the composition at a specific location.
Documented attack patterns abuse exactly the kind of access paste_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 paste_items:
{
"version": "1",
"default": "deny",
"tools": {
"paste_items": {
"limits": [
{
"counter": "paste_items_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}paste_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.
Paste items from clipboard at edit cursor. 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 paste_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.
paste_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 paste_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 paste_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.
paste_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.