Stop the music. Use for stop, pause, halt, wait, or cease playback.
AI agents invoke dsl_stop 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 tool executes a command that controls external media playback state in REAPER. While stopping playback is not destructive (no data is lost or irreversibly modified) and cannot cause financial harm, it is an Execute-category action because it triggers an external operation whose effects depend on the current state of the application.
From the tool's definition The tool description states "Stop the music" and "stop, pause, halt, wait, or cease playback", indicating it triggers an immediate action that controls REAPER's playback state.
Documented attack patterns abuse exactly the kind of access dsl_stop 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_stop:
{
"version": "1",
"default": "deny",
"tools": {
"dsl_stop": {
"limits": [
{
"counter": "dsl_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} dsl_stop 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.
Stop the music. Use for stop, pause, halt, wait, or cease playback. 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_stop: 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_stop 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_stop 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_stop. 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_stop 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.