AI agents use item_move 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.
Moving an item to a new position modifies project state but does not permanently destroy data or execute arbitrary code. It is reversible (can be undone or moved again), making it a Write operation rather than Execute or Destructive. Severity is medium because misuse could disrupt a music project's arrangement, but the effect is recoverable and limited in scope to a single item's position.
From the tool's definition Tool name 'item_move' and description 'Move item to new position' indicate modification of item placement within a REAPER project. This is a reversible state change to project data.
Documented attack patterns abuse exactly the kind of access item_move 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:
{
"version": "1",
"default": "deny",
"tools": {
"item_move": {
"limits": [
{
"counter": "item_move_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}item_move 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 new position. 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: 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 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 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. 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 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.