AI agents use insert_midi_notes 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.
The tool creates or adds MIDI note data to a music project—a Write operation. It is reversible (notes can be deleted or edited), so it does not qualify as Destructive. The severity is high because an AI agent inserting arbitrary MIDI notes could substantially alter a user's musical work, corrupt compositional intent, or create unusable results.
From the tool's definition Tool name 'insert_midi_notes' indicates creation of MIDI data in a REAPER project. Sibling tools like 'apply_changes', 'apply_mix_balance', and 'apply_master_match' establish that this server modifies audio projects.
Attacks that exploit this kind of access
insert_midi_notes. 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.
Register the Orpheus MCP server in PolicyLayer and add a rule for insert_midi_notes: 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.
insert_midi_notes 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 insert_midi_notes 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 insert_midi_notes. 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.
insert_midi_notes 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →