AI agents use set_item_position to create or update resources in Reaper Reapy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reaper Reapy environment.
The tool modifies item position in REAPER, which is a reversible change (items can be repositioned again). This qualifies as Write rather than Execute (no code/script execution) or Destructive (position changes are undoable). Severity is medium because misuse could corrupt a user's project timeline or arrangement, but changes can be undone via undo functionality in REAPER.
From the tool's definition Tool name 'set_item_position' indicates modification of existing item properties. Sibling tools include 'create_track', 'add_fx', 'create_midi_item', and 'delete_item', establishing this server's pattern of mutating REAPER DAW state.
Documented attack patterns abuse exactly the kind of access set_item_position gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for set_item_position:
{
"version": "1",
"default": "deny",
"tools": {
"set_item_position": {
"limits": [
{
"counter": "set_item_position_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_item_position 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.
set_item_position. It is categorised as a Write tool in the Reaper Reapy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for set_item_position: 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 Reapy. Nothing to install.
set_item_position 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 set_item_position 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 set_item_position. 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.
set_item_position is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.