Medium Risk

dsl_track_duplicate

dsl_track_duplicate

How to control dsl_track_duplicate ↓

AI agents use dsl_track_duplicate to create or update resources in REAPER MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your REAPER MCP Server environment.

Medium Risk

Duplicating a track in REAPER creates new data (copied track with settings, automation, and effects) but is reversible—the duplicated track can be deleted. This fits the Write category (creates/modifies data reversibly) rather than Destructive. Severity is medium because duplicating tracks could consume disk space or clutter a project if done excessively, but the operation itself is non-destructive and can be undone.

From the tool's definition Tool named 'dsl_track_duplicate' on REAPER MCP server that exposes track management operations. The 'duplicate' action creates a copy of audio track data, which is a reversible modification operation.

Documented attack patterns abuse exactly the kind of access dsl_track_duplicate 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_track_duplicate:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "dsl_track_duplicate": {
      "limits": [
        {
          "counter": "dsl_track_duplicate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

dsl_track_duplicate stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

  1. Create a free account and register REAPER MCP Server — 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the dsl_track_duplicate tool do? +

dsl_track_duplicate. It is categorised as a Write tool in the REAPER MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dsl_track_duplicate? +

Register the REAPER MCP Server MCP server in PolicyLayer and add a rule for dsl_track_duplicate: 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.

What risk level is dsl_track_duplicate? +

dsl_track_duplicate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dsl_track_duplicate? +

Yes. Add a rate_limit block to the dsl_track_duplicate 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 dsl_track_duplicate completely? +

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

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

Enforce policy on every REAPER MCP Server tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.