Move item to different track.
AI agents use item_move_to_track to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
This action creates or modifies the project structure reversibly—items can be moved back to their original tracks, undoing the change. It does not execute arbitrary code, trigger external operations with unpredictable effects, delete data permanently, or involve financial transactions. The blast radius is confined to project arrangement and is easily reversible, making it Write rather than Execute or Destructive.
From the tool's definition Tool name 'item_move_to_track' and description 'Move item to different track' indicate the tool modifies the arrangement of audio/MIDI items within a REAPER project by relocating them between tracks.
Documented attack patterns abuse exactly the kind of access item_move_to_track gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for item_move_to_track:
{
"version": "1",
"default": "deny",
"tools": {
"item_move_to_track": {
"limits": [
{
"counter": "item_move_to_track_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}item_move_to_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.
Move item to different track. It is categorised as a Write tool in the ReaperMCP 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 item_move_to_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 ReaperMCP. Nothing to install.
item_move_to_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 item_move_to_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 item_move_to_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.
item_move_to_track is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, 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.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.