AI agents call list_tracks to retrieve information from Orpheus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about the current track tree in a REAPER project with no side effects. It enables analysis and understanding of project structure, which is essential for the agent to make informed decisions about modifications, but it does not itself create, modify, or delete any audio data or project state.
From the tool's definition The tool description states it retrieves track metadata—"name, vol/pan, mute/solo, role, FX-chain names, item count"—without modifying any state. The verb "list" and the structured data retrieval pattern confirm this is a read-only operation.
Attacks that exploit this kind of access
The typed track tree: name, vol/pan, mute/solo, role, FX-chain names, item count. It is categorised as a Read tool in the Orpheus MCP Server, which means it retrieves data without modifying state.
Register the Orpheus MCP server in PolicyLayer and add a rule for 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 Orpheus. Nothing to install.
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 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 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.
list_tracks is provided by the Orpheus MCP server (mal0ware/orpheus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →