create_track · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What create_track does on Scythe MCP REAPER

AI agents use create_track to create or update resources in Scythe MCP REAPER — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scythe MCP REAPER environment.

WHY IT NEEDS A POLICY

Why create_track needs a policy

Creating a track is a reversible modification operation that adds new data to the REAPER project. It does not execute arbitrary code, delete data permanently, move money, or trigger external system operations. It falls squarely into the Write category—data creation without side effects beyond the DAW's own state.

From the tool's definition Tool name 'create_track' and description 'Create a new track' indicate creation of new data within REAPER DAW. The sibling tools (add_bass_track, add_drum_track, add_melody_track) confirm the pattern of creating/modifying track structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_track Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_track": {
      "limits": [
        {
          "counter": "create_track_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 create_track

What does the create_track tool do? +

Create a new track. It is categorised as a Write tool in the Scythe MCP REAPER MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_track? +

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

create_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_track? +

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

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

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