AI agents invoke toggle_master_mute to trigger actions in Reaper Reapy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Toggling the master mute affects all audio output in the DAW session immediately. It is an operational/control action (triggering an external operation in REAPER) rather than a simple data write. The empty description lowers confidence, but the name strongly implies a state-change execution on the master bus.
From the tool's definition Tool name 'toggle_master_mute' — no description provided; name implies toggling the master mute state in REAPER DAW.
Documented attack patterns abuse exactly the kind of access toggle_master_mute gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for toggle_master_mute:
{
"version": "1",
"default": "deny",
"tools": {
"toggle_master_mute": {
"limits": [
{
"counter": "toggle_master_mute_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}toggle_master_mute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
toggle_master_mute. It is categorised as a Execute tool in the Reaper Reapy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for toggle_master_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 Reaper Reapy. Nothing to install.
toggle_master_mute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the toggle_master_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 toggle_master_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.
toggle_master_mute is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.