Arm or disarm a track for recording.
AI agents use arm_track to create or update resources in Reaper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reaper environment.
This tool modifies the armed/disarmed state of a track in REAPER DAW. It changes a track's recording readiness state, which is a reversible write operation — it can easily be toggled back. No data is deleted, no code is executed, and no financial transactions occur. Misuse has minimal blast radius as it only affects whether a track is ready to record.
From the tool's definition Arm or disarm a track for recording
Documented attack patterns abuse exactly the kind of access arm_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for arm_track:
{
"version": "1",
"default": "deny",
"tools": {
"arm_track": {
"limits": [
{
"counter": "arm_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Arm or disarm a track for recording. It is categorised as a Write tool in the Reaper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 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 Reaper. Nothing to install.
arm_track is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
arm_track is provided by the Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reaper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.