AI agents use add_eq to create or update resources in Reaper — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reaper environment.
This tool creates or modifies track configuration by adding an EQ effect, which is a reversible change (the EQ can be removed). It does not execute arbitrary code, delete data irreversibly, or move money. It qualifies as Write rather than Execute because it applies a pre-built effect rather than executing user-supplied scripts or commands.
From the tool's definition Tool name 'add_eq' and description 'Add ReaEQ to a track' indicate creation/modification of track effects. ReaEQ is REAPER's parametric equalizer plugin that modifies track audio processing settings.
Documented attack patterns abuse exactly the kind of access add_eq gives an agent:
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 add_eq:
{
"version": "1",
"default": "deny",
"tools": {
"add_eq": {
"limits": [
{
"counter": "add_eq_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_eq 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.
Add ReaEQ to a track. 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.
Register the Reaper MCP server in PolicyLayer and add a rule for add_eq: 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.
add_eq 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 add_eq 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 add_eq. 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.
add_eq 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.
Start from Reaper, 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.
158 Reaper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.