AI agents use insert_audio_item to create or update resources in Reaper Reapy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reaper Reapy environment.
The tool inserts audio items into a REAPER project, which creates or modifies project state reversibly. This is a Write operation (not Destructive, as audio item insertion can be undone via undo/delete). Severity is medium because inserting large or unwanted audio could disrupt a project workflow or cause data loss if combined with other operations, but it's not irreversible or destructive by itself.
From the tool's definition Tool name 'insert_audio_item' indicates creation/insertion of audio content. Server context shows REAPER DAW audio operations. Sibling tools include 'create_track', 'create_midi_item', 'add_fx' which are clearly Write operations.
Documented attack patterns abuse exactly the kind of access insert_audio_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for insert_audio_item:
{
"version": "1",
"default": "deny",
"tools": {
"insert_audio_item": {
"limits": [
{
"counter": "insert_audio_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}insert_audio_item 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.
insert_audio_item. It is categorised as a Write tool in the Reaper Reapy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for insert_audio_item: 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 Reapy. Nothing to install.
insert_audio_item 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 insert_audio_item 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 insert_audio_item. 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.
insert_audio_item is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.