AI agents use track_set_mute to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
Muting/unmuting a track is a reversible state change that modifies the project configuration. It does not execute external code, delete data irreversibly, or move money. The blast radius is medium because an agent could accidentally mute critical tracks in a complex session, disrupting workflow and potentially causing data loss if the user saves without noticing—though the change itself is fully reversible.
From the tool's definition Tool name: 'track_set_mute' with description 'Mute/unmute a track.' This modifies track state (mute status) reversibly without deleting or destroying data.
Documented attack patterns abuse exactly the kind of access track_set_mute 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 track_set_mute:
{
"version": "1",
"default": "deny",
"tools": {
"track_set_mute": {
"limits": [
{
"counter": "track_set_mute_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_set_mute 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.
Free to start. No card required.
Mute/unmute a track. It is categorised as a Write tool in the ReaperMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper MCP server in PolicyLayer and add a rule for track_set_mute: 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.
track_set_mute is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the track_set_mute 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 track_set_mute. 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.
track_set_mute 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.