goto_position · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What goto_position does on Scythe MCP REAPER

AI agents invoke goto_position to trigger actions in Scythe MCP 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.

WHY IT NEEDS A POLICY

Why goto_position needs a policy

This tool moves the playback/edit cursor in REAPER to a specific position. It is not a simple read, nor does it create/modify/delete data. It triggers an external action in the DAW (changing transport position), making it Execute. Blast radius is low since it only repositions the cursor without modifying any project data.

From the tool's definition 'Move cursor to a specific position' — triggers an external operation in the REAPER DAW via OSC/ReaScript integration

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

goto_position Rate-limited

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

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Scythe MCP REAPER, so you can run agents against it safely.

FAQ

Questions about goto_position

What does the goto_position tool do? +

Move cursor to a specific position. It is categorised as a Execute tool in the Scythe MCP 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 goto_position? +

Register the Scythe MCP REAPER MCP server in PolicyLayer and add a rule for goto_position: 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 Scythe MCP REAPER. Nothing to install.

What risk level is goto_position? +

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

Can I rate-limit goto_position? +

Yes. Add a rate_limit block to the goto_position 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 goto_position completely? +

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

goto_position is provided by the Scythe MCP REAPER MCP server (yura9011/scythe_mcp_reaper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.