create_chord_progression · Orpheus MCP: Risk & Policy

WHAT IT DOES

What create_chord_progression does on Orpheus

AI agents use create_chord_progression 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 create_chord_progression needs a policy

The tool generates and writes new MIDI chord progression content to the project. This is a reversible create operation (MIDI clips can be deleted/undone), not destructive. It does not execute arbitrary code or trigger external side effects, nor does it delete/overwrite existing data.

From the tool's definition Tool creates MIDI data (voiced, in-key, tempo-correct MIDI) which is data generation and persistent modification of a REAPER music project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_chord_progression Rate-limited

create_chord_progression 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": {
    "create_chord_progression": {
      "limits": [
        {
          "counter": "create_chord_progression_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 create_chord_progression

What does the create_chord_progression tool do? +

Text chord names ('Cm7, Fm7, Bb7') → voiced, in-key, tempo-correct MIDI. 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 create_chord_progression? +

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

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

Can I rate-limit create_chord_progression? +

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

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

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