Get the current playback state.
AI agents call get_play_state to retrieve information from Reaper without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves information about REAPER's current playback state (playing, stopped, paused, etc.). It has no side effects, does not execute commands, does not modify data, and does not trigger external operations. It is a simple status query, making it a Read category tool with low severity as misuse would only result in retrieving potentially stale or redundant status information.
From the tool's definition Tool name 'get_play_state' and description 'Get the current playback state' indicate a read-only query operation that retrieves playback status without modifying any state or triggering any actions.
Documented attack patterns abuse exactly the kind of access get_play_state 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 get_play_state:
{
"version": "1",
"default": "deny",
"tools": {
"get_play_state": {}
}
}get_play_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the current playback state. It is categorised as a Read tool in the Reaper MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for get_play_state: 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.
get_play_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_play_state 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 get_play_state. 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.
get_play_state 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.