Zoom the arrange view to the time selection.
AI agents invoke zoom_to_selection to trigger actions in Reaper. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers a UI/view action in the REAPER DAW — adjusting the zoom level of the arrange view. It doesn't read, write, or delete data, but it executes an external operation (controlling the DAW interface). Misuse potential is minimal as it only affects the view state.
From the tool's definition Zoom the arrange view to the time selection
Documented attack patterns abuse exactly the kind of access zoom_to_selection 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 zoom_to_selection:
{
"version": "1",
"default": "deny",
"tools": {
"zoom_to_selection": {
"limits": [
{
"counter": "zoom_to_selection_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}zoom_to_selection stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Zoom the arrange view to the time selection. It is categorised as a Execute tool in the Reaper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Reaper MCP server in PolicyLayer and add a rule for zoom_to_selection: 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.
zoom_to_selection is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the zoom_to_selection 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 zoom_to_selection. 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.
zoom_to_selection 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.