Low Risk

selection_select_all_items

Select all items.

How to control selection_select_all_items ↓

What selection_select_all_items does on ReaperMCP

AI agents call selection_select_all_items to retrieve information from ReaperMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why selection_select_all_items needs a policy

Selecting items in a DAW is a non-destructive UI state change that does not modify, delete, or move any audio/MIDI data. It sets the selection state so other tools can act on those items. Closest to Read (retrieves/marks state) with no data side effects. Severity is low as misuse only results in unintended items being selected, which can be undone or overridden easily.

From the tool's definition Select all items — this is a UI selection action that highlights/marks items for subsequent operations

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access selection_select_all_items gives an agent:

How to control selection_select_all_items

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_select_all_items:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "selection_select_all_items": {}
  }
}

selection_select_all_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register ReaperMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about selection_select_all_items

What does the selection_select_all_items tool do? +

Select all items. It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on selection_select_all_items? +

Register the Reaper MCP server in PolicyLayer and add a rule for selection_select_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.

What risk level is selection_select_all_items? +

selection_select_all_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit selection_select_all_items? +

Yes. Add a rate_limit block to the selection_select_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.

How do I block selection_select_all_items completely? +

Set action: deny in the PolicyLayer policy for selection_select_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.

What MCP server provides selection_select_all_items? +

selection_select_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.

Enforce policy on every ReaperMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.