Get all selected media items.
AI agents call get_selected_items to retrieve information from Reaper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the current state of the REAPER DAW to retrieve selected media items. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes. The action has no side effects and poses minimal security risk—it only exposes information already visible in the DAW interface.
From the tool's definition Tool name 'get_selected_items' and description 'Get all selected media items' indicate a retrieval operation with no modification of state.
Documented attack patterns abuse exactly the kind of access get_selected_items gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper, and nothing reaches the server without passing your rules. This is the rule we recommend for get_selected_items:
{
"version": "1",
"default": "deny",
"tools": {
"get_selected_items": {}
}
} get_selected_items is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all selected media items. It is categorised as a Read tool in the Reaper MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for get_selected_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 Reaper. Nothing to install.
get_selected_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_selected_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 get_selected_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.
get_selected_items is provided by the Reaper MCP server (twelvetake-studios/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reaper, 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.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.