track_fx_set_enabled

THE RISK

Medium Risk

Why track_fx_set_enabled needs a policy

This tool modifies the enabled/disabled state of an FX plugin on a track. This is a reversible state change (it can be toggled back), making it a Write operation. Misuse has low blast radius as it only affects a plugin's active state in a DAW project.

From the tool's definition Enable or disable an FX plugin

Documented attack patterns abuse exactly the kind of access track_fx_set_enabled gives an agent:

POLICY

How to control track_fx_set_enabled

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 track_fx_set_enabled:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "track_fx_set_enabled": {
      "limits": [
        {
          "counter": "track_fx_set_enabled_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Reaper — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Reaper tools

Destructive clear_envelope Delete all points from an envelope. Destructive clear_fx_envelope Clear all automation points from an FX parameter envelope. Destructive clear_midi_item Delete all MIDI notes from an item. Destructive delete_envelope_point Delete an envelope point. Destructive delete_fx_envelope_point delete_fx_envelope_point Destructive delete_item Delete a media item. Destructive delete_marker Delete a marker by index. Destructive delete_midi_note Delete a MIDI note from an item.

All 158 Reaper tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about track_fx_set_enabled

What does the track_fx_set_enabled tool do? +

Enable or disable an FX plugin. It is categorised as a Write tool in the Reaper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on track_fx_set_enabled? +

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

What risk level is track_fx_set_enabled? +

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

Can I rate-limit track_fx_set_enabled? +

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

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

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

Enforce policy on every Reaper tool call.

Start from Reaper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →