set_track_volume_pan · Orpheus MCP: Risk & Policy

WHAT IT DOES

What set_track_volume_pan does on Orpheus

AI agents use set_track_volume_pan to create or update resources in Orpheus — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Orpheus environment.

WHY IT NEEDS A POLICY

Why set_track_volume_pan needs a policy

This tool modifies audio project parameters (volume and pan) but does not delete, execute arbitrary code, move money, or create permanent side effects. Changes to fader and pan are typical Write operations—they alter project state reversibly. Severity is medium because misuse could degrade a mix significantly, requiring re-tuning, but the changes are easily undone by resetting faders or using undo.

From the tool's definition "Set fader/pan" directly modifies track volume and pan parameters in REAPER, which are reversible mix settings. The tool accepts explicit volume and pan values, indicating it creates or modifies audio project state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_track_volume_pan Rate-limited

set_track_volume_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_track_volume_pan": {
      "limits": [
        {
          "counter": "set_track_volume_pan_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Orpheus, so you can run agents against it safely.

FAQ

Questions about set_track_volume_pan

What does the set_track_volume_pan tool do? +

Set fader/pan. Accepts fuzzy values ('-6dB', '+3', '50%', 'L50', 'center'). It is categorised as a Write tool in the Orpheus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_track_volume_pan? +

Register the Orpheus MCP server in PolicyLayer and add a rule for set_track_volume_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 Orpheus. Nothing to install.

What risk level is set_track_volume_pan? +

set_track_volume_pan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_track_volume_pan? +

Yes. Add a rate_limit block to the set_track_volume_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.

How do I block set_track_volume_pan completely? +

Set action: deny in the PolicyLayer policy for set_track_volume_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.

What MCP server provides set_track_volume_pan? +

set_track_volume_pan is provided by the Orpheus MCP server (mal0ware/orpheus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.