Get a list of all currently selected tracks with their info.
AI agents call selection_get_selected_tracks 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.
This is a query operation that retrieves the current state of selected tracks from REAPER. It performs no modification, deletion, execution, or financial operation. The 'get' prefix and explicit description clearly indicate data retrieval only. The blast radius of misuse is minimal—an AI agent accessing this information cannot directly harm the project or any external systems.
From the tool's definition Tool name uses 'get' verb and description states 'Get a list of all currently selected tracks with their info' — retrieves track information with no side effects or modifications.
Documented attack patterns abuse exactly the kind of access selection_get_selected_tracks 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_get_selected_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"selection_get_selected_tracks": {}
}
}selection_get_selected_tracks 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 a list of all currently selected tracks with their info. It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for selection_get_selected_tracks: 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_get_selected_tracks 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 selection_get_selected_tracks 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_get_selected_tracks. 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_get_selected_tracks 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.