Show what's in your project. Use when users ask what tracks exist or want an overview.
AI agents call dsl_list_tracks to retrieve information from REAPER MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about tracks in a REAPER project. It performs no modifications, deletions, or side effects—it is purely informational. This is a classic Read operation: passive data enumeration with no impact on the audio project state.
From the tool's definition Tool name 'dsl_list_tracks' and description 'Show what's in your project. Use when users ask what tracks exist or want an overview.' indicate a retrieval operation that queries project state without modifying, deleting, or executing external operations.
Documented attack patterns abuse exactly the kind of access dsl_list_tracks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and REAPER MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dsl_list_tracks:
{
"version": "1",
"default": "deny",
"tools": {
"dsl_list_tracks": {}
}
}dsl_list_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.
Show what's in your project. Use when users ask what tracks exist or want an overview. It is categorised as a Read tool in the REAPER MCP Server MCP Server, which means it retrieves data without modifying state.
Register the REAPER MCP Server MCP server in PolicyLayer and add a rule for dsl_list_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 REAPER MCP Server. Nothing to install.
dsl_list_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 dsl_list_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 dsl_list_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.
dsl_list_tracks is provided by the REAPER MCP Server MCP server (shiehn/total-reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 REAPER MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 REAPER MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.