AI agents invoke transport_play to trigger actions in ReaperMCP. 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 an external operation (starting REAPER's playback transport) whose effects depend on the current project state and session. It is not a read-only query, nor does it modify project data persistently, nor does it destroy or move financial resources. It is an Execute action because it triggers a real-world effect (audio playback) via the music production software.
From the tool's definition Tool name 'transport_play' and description 'Start playback' indicate execution of a playback action in REAPER, triggering audio output and transport control operations.
Documented attack patterns abuse exactly the kind of access transport_play gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for transport_play:
{
"version": "1",
"default": "deny",
"tools": {
"transport_play": {
"limits": [
{
"counter": "transport_play_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}transport_play 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 playback. It is categorised as a Execute tool in the ReaperMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Reaper MCP server in PolicyLayer and add a rule for transport_play: 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 ReaperMCP. Nothing to install.
transport_play 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 transport_play 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 transport_play. 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.
transport_play is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, 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.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.