Explode all takes of a media item in place (each take becomes its own overlapping item).
AI agents use explode_takes 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 new media items and modifies the project structure by converting takes into separate overlapping items. While the operation is technically reversible via undo, it materially alters the project state and arrangement in a way that cannot be undone by the tool itself (Write category). It is not Destructive because the original take data is not deleted, merely reorganized.
From the tool's definition Tool description states it will 'Explode all takes of a media item in place (each take becomes its own overlapping item)' - this modifies the project structure by creating new items from existing takes, permanently reorganizing the media layout.
Documented attack patterns abuse exactly the kind of access explode_takes 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 explode_takes:
{
"version": "1",
"default": "deny",
"tools": {
"explode_takes": {
"limits": [
{
"counter": "explode_takes_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}explode_takes 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.
Explode all takes of a media item in place (each take becomes its own overlapping item). 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 explode_takes: 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.
explode_takes 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 explode_takes 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 explode_takes. 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.
explode_takes 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.