record · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What record does on Scythe MCP REAPER

AI agents invoke record 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 record needs a policy

The 'record' tool executes a state-changing action on REAPER (starting audio/MIDI recording). This is Execute-class because it triggers an external operation whose effects depend on the DAW's current state and configuration. While not destructive by itself, recording can overwrite existing takes/clips and captures live audio in an uncontrolled manner.

From the tool's definition Tool performs 'Start recording' action on REAPER DAW via OSC/ReaScript integration, which is a consequential operation that triggers external audio/MIDI capture on a digital audio workstation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record Rate-limited

record 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": {
    "record": {
      "limits": [
        {
          "counter": "record_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 record

What does the record tool do? +

Start recording. 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 record? +

Register the Scythe MCP REAPER MCP server in PolicyLayer and add a rule for record: 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 record? +

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

Can I rate-limit record? +

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

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

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