Get the master/parent send state of a track.
AI agents call get_track_master_send 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 retrieves information about a track's master/parent send state. The verb 'get' combined with the phrase 'state of' clearly indicates a data retrieval operation with no side effects. It does not create, modify, delete, or execute any operations—it only queries existing configuration. This is a classic Read category tool.
From the tool's definition Tool name 'get_track_master_send' and description 'Get the master/parent send state of a track' indicate a read-only query operation that retrieves state information without modifying anything.
Documented attack patterns abuse exactly the kind of access get_track_master_send 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_track_master_send:
{
"version": "1",
"default": "deny",
"tools": {
"get_track_master_send": {}
}
}get_track_master_send 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 master/parent send state of a track. 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_track_master_send: 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_track_master_send 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_track_master_send 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_track_master_send. 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_track_master_send 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.