add_envelope_point
AI agents use add_envelope_point 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 a new envelope point, which modifies the project state but is reversible (the point can be deleted or the action undone). It does not execute arbitrary code, delete data irreversibly, or move financial assets. However, confidence is reduced from 0.85 to 0.75 because the description is empty, requiring inference from naming convention and sibling context.
From the tool's definition Tool name 'add_envelope_point' indicates creation of a new envelope control point in REAPER DAW. Sibling tools like 'add_fx_envelope_point', 'add_compressor', 'add_eq', and 'add_midi_note' all perform reversible write operations within the DAW.
Documented attack patterns abuse exactly the kind of access add_envelope_point 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_envelope_point:
{
"version": "1",
"default": "deny",
"tools": {
"add_envelope_point": {
"limits": [
{
"counter": "add_envelope_point_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_envelope_point 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_envelope_point. 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_envelope_point: 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_envelope_point 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_envelope_point 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_envelope_point. 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_envelope_point 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.