create_midi_item · Orpheus MCP: Risk & Policy

WHAT IT DOES

What create_midi_item does on Orpheus

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

This tool creates new MIDI data (items/takes) in a music project, which modifies the project state. While creation is reversible (unlike deletion), it constitutes a Write action that generates new artifacts. Severity is high because an AI agent with unconstrained use could flood a project with unwanted MIDI data, corrupt the project structure, or overwrite carefully crafted musical content if misapplied.

From the tool's definition Tool description states 'Create a MIDI item/take' — the verb 'Create' indicates irreversible generation of new musical data within the REAPER project.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_midi_item Rate-limited

create_midi_item 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_midi_item": {
      "limits": [
        {
          "counter": "create_midi_item_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_midi_item

What does the create_midi_item tool do? +

Create a MIDI item/take over a bar range; returns a stable take identity. 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_midi_item? +

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

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

Can I rate-limit create_midi_item? +

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

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

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