AI agents use send_set_pan to create or update resources in ReaperMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ReaperMCP environment.
The tool sets/modifies a mixing parameter (pan on an audio send), which is a Write operation—it alters state reversibly without executing arbitrary code or deleting data. Severity is medium because misconfiguration could affect audio output quality or routing in unexpected ways, but changes are easily undone.
From the tool's definition Tool name 'send_set_pan' and description 'Set send pan' indicate the tool modifies audio mixing parameters (pan setting on a send channel). This is a reversible configuration change to a mixing parameter.
Documented attack patterns abuse exactly the kind of access send_set_pan 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 send_set_pan:
{
"version": "1",
"default": "deny",
"tools": {
"send_set_pan": {
"limits": [
{
"counter": "send_set_pan_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_set_pan stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Set send pan. It is categorised as a Write tool in the ReaperMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reaper MCP server in PolicyLayer and add a rule for send_set_pan: 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.
send_set_pan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_set_pan 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 send_set_pan. 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.
send_set_pan 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.