arm_track · Scythe MCP REAPER MCP: Risk & Policy

WHAT IT DOES

What arm_track does on Scythe MCP REAPER

AI agents use arm_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 arm_track needs a policy

Arming/disarming a track modifies the recording state but does not create, delete, or execute arbitrary code. It is a standard DAW control that changes track configuration reversibly. While it could affect what gets recorded in future operations, the action itself is non-destructive and limited to enabling/disabling recording on a specific track.

From the tool's definition Tool name 'arm_track' and description 'Arm or disarm a track for recording' indicate state modification of track recording settings. This is a reversible change to DAW configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

arm_track Rate-limited

arm_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": {
    "arm_track": {
      "limits": [
        {
          "counter": "arm_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 arm_track

What does the arm_track tool do? +

Arm or disarm a track for recording. 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 arm_track? +

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

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

Can I rate-limit arm_track? +

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

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

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