Start recording. Use for 'record', 'start recording', 'rec'.
AI agents invoke dsl_record to trigger actions in REAPER MCP Server. 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.
This is Execute rather than Write because it triggers a complex, time-dependent external operation (audio capture) whose side effects extend beyond simple data creation—it commits audio stream data to storage and modifies the state of a professional audio system.
From the tool's definition Tool initiates recording functionality with 'Start recording' description. This triggers an external audio capture operation whose effects depend on context (what audio sources are active, duration, storage location).
Documented attack patterns abuse exactly the kind of access dsl_record gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and REAPER MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dsl_record:
{
"version": "1",
"default": "deny",
"tools": {
"dsl_record": {
"limits": [
{
"counter": "dsl_record_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dsl_record 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.
Start recording. Use for 'record', 'start recording', 'rec'. It is categorised as a Execute tool in the REAPER MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the REAPER MCP Server MCP server in PolicyLayer and add a rule for dsl_record: 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 MCP Server. Nothing to install.
dsl_record 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 dsl_record 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 dsl_record. 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.
dsl_record is provided by the REAPER MCP Server MCP server (shiehn/total-reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 45 REAPER MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
45 REAPER MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.