Clear the peak hold indicators on all tracks (including master).
AI agents use clear_all_peak_indicators 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.
Clearing peak hold indicators resets a UI/display state in the DAW. This is a write/modification action (resetting indicator state), but it has no effect on audio data, MIDI, or project content. The blast radius is minimal since it only affects visual meters and is easily reversible by simply playing audio again.
From the tool's definition Clear the peak hold indicators on all tracks (including master)
Documented attack patterns abuse exactly the kind of access clear_all_peak_indicators 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 clear_all_peak_indicators:
{
"version": "1",
"default": "deny",
"tools": {
"clear_all_peak_indicators": {
"limits": [
{
"counter": "clear_all_peak_indicators_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}clear_all_peak_indicators 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.
Clear the peak hold indicators on all tracks (including master). 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 clear_all_peak_indicators: 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.
clear_all_peak_indicators 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 clear_all_peak_indicators 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 clear_all_peak_indicators. 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.
clear_all_peak_indicators 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.