zoom_to_project

THE RISK

High Risk

Why zoom_to_project needs a policy

This tool triggers a UI/view action in the REAPER DAW — adjusting the zoom level of the arrange view. It doesn't read data, write/modify project content, or delete anything, but it does execute an external operation (controlling DAW interface state). The blast radius is minimal as it only affects the display view.

From the tool's definition Zoom the arrange view to show the entire project

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access zoom_to_project gives an agent:

POLICY

How to control zoom_to_project

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_project:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zoom_to_project": {
      "limits": [
        {
          "counter": "zoom_to_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

zoom_to_project 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.

Create a free account and register Reaper — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Reaper tools

Destructive clear_envelope Delete all points from an envelope. Destructive clear_fx_envelope Clear all automation points from an FX parameter envelope. Destructive clear_midi_item Delete all MIDI notes from an item. Destructive delete_envelope_point Delete an envelope point. Destructive delete_fx_envelope_point delete_fx_envelope_point Destructive delete_item Delete a media item. Destructive delete_marker Delete a marker by index. Destructive delete_midi_note Delete a MIDI note from an item.

All 158 Reaper tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Reaper → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about zoom_to_project

What does the zoom_to_project tool do? +

Zoom the arrange view to show the entire project. 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.

How do I enforce a policy on zoom_to_project? +

Register the Reaper MCP server in PolicyLayer and add a rule for zoom_to_project: 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.

What risk level is zoom_to_project? +

zoom_to_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit zoom_to_project? +

Yes. Add a rate_limit block to the zoom_to_project 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.

How do I block zoom_to_project completely? +

Set action: deny in the PolicyLayer policy for zoom_to_project. 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.

What MCP server provides zoom_to_project? +

zoom_to_project 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.

Enforce policy on every Reaper tool call.

Start from Reaper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →