Deselect all media items.
AI agents use selection_deselect_all_items 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.
Deselecting items modifies the current state of the REAPER project (which items are selected) in a reversible manner. This is a write operation—it changes data (selection metadata) without destroying content or executing external code. The blast radius is minimal since selection state changes are easily undone and affect only the UI state, not audio data or project structure.
From the tool's definition Tool name 'selection_deselect_all_items' and description 'Deselect all media items' indicate modification of selection state in REAPER's UI/session.
Documented attack patterns abuse exactly the kind of access selection_deselect_all_items 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 selection_deselect_all_items:
{
"version": "1",
"default": "deny",
"tools": {
"selection_deselect_all_items": {
"limits": [
{
"counter": "selection_deselect_all_items_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}selection_deselect_all_items 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.
Deselect all media items. 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 selection_deselect_all_items: 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.
selection_deselect_all_items 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 selection_deselect_all_items 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 selection_deselect_all_items. 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.
selection_deselect_all_items 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.