select_track · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What select_track does on Scythe MCP REAPER

AI agents use select_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 select_track needs a policy

Selecting a track modifies the application state (the current selection) in the DAW. It is reversible and has minimal blast radius, but it does change state rather than purely reading data. Confidence is moderate because the description is very brief and lacks detail.

From the tool's definition Select a track

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

select_track Rate-limited

select_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": {
    "select_track": {
      "limits": [
        {
          "counter": "select_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 select_track

What does the select_track tool do? +

Select a 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 select_track? +

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

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

Can I rate-limit select_track? +

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

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

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