Get information about REAPER. Note: OSC is primarily for sending commands.
AI agents call get_session_info to retrieve information from Scythe MCP REAPER without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries session metadata from REAPER without creating, modifying, deleting, or executing any operations. It has no side effects and falls squarely into the Read category. Severity is low because exposure of session information poses minimal risk to system integrity or the DAW's state.
From the tool's definition Tool name 'get_session_info' and description 'Get information about REAPER' indicate data retrieval with no modification or execution of commands. The note clarifies that this tool retrieves information rather than sending commands.
Attacks that exploit this kind of access
Get information about REAPER. Note: OSC is primarily for sending commands. It is categorised as a Read tool in the Scythe MCP REAPER MCP Server, which means it retrieves data without modifying state.
Register the Scythe MCP REAPER MCP server in PolicyLayer and add a rule for get_session_info: 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 Scythe MCP REAPER. Nothing to install.
get_session_info 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_session_info 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_session_info. 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_session_info is provided by the Scythe MCP REAPER MCP server (yura9011/scythe_mcp_reaper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →