play_stop_record · Orpheus MCP: Risk & Policy

WHAT IT DOES

What play_stop_record does on Orpheus

AI agents invoke play_stop_record to trigger actions in Orpheus. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why play_stop_record needs a policy

This tool executes commands that trigger side effects in REAPER's audio engine. While not immediately destructive or financial, it operates external systems and can modify project state (recording creates new audio data). It does not merely read data—it initiates actions.

From the tool's definition Tool performs transport control actions ('play', 'stop', 'record') via REAPER's Main_OnCommand action IDs. These trigger external operations (audio playback, recording state) whose effects depend on the command argument and current project state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

play_stop_record Rate-limited

play_stop_record stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "play_stop_record": {
      "limits": [
        {
          "counter": "play_stop_record_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 play_stop_record

What does the play_stop_record tool do? +

Transport control: 'play' | 'stop' | 'record', via Main_OnCommand action IDs. It is categorised as a Execute tool in the Orpheus MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on play_stop_record? +

Register the Orpheus MCP server in PolicyLayer and add a rule for play_stop_record: 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 play_stop_record? +

play_stop_record is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit play_stop_record? +

Yes. Add a rate_limit block to the play_stop_record 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 play_stop_record completely? +

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

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