Set REAPER's ripple edit mode.
AI agents use project_set_ripple_mode 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 tool changes a project setting in REAPER (ripple editing mode state), which is a reversible modification. It does not execute arbitrary code, delete data, or move money. While it alters project state, the change can be immediately undone, placing it in Write rather than Execute or Destructive.
From the tool's definition Tool name 'project_set_ripple_mode' and description 'Set REAPER's ripple edit mode' indicate it modifies a REAPER project setting. Ripple edit mode is a reversible configuration option (can be toggled on/off), not a destructive operation.
Documented attack patterns abuse exactly the kind of access project_set_ripple_mode 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 project_set_ripple_mode:
{
"version": "1",
"default": "deny",
"tools": {
"project_set_ripple_mode": {
"limits": [
{
"counter": "project_set_ripple_mode_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}project_set_ripple_mode 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.
Set REAPER's ripple edit mode. 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 project_set_ripple_mode: 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.
project_set_ripple_mode 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 project_set_ripple_mode 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 project_set_ripple_mode. 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.
project_set_ripple_mode 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.