Get MIDI note number to name mapping (C4=60, etc.).
AI agents call midi_get_note_names to retrieve information from ReaperMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple lookup or query of MIDI note numbering conventions—a read-only operation that provides reference information. There are no side effects, no data modification, no code execution, and no destructive or financial implications. The low severity reflects minimal risk even if misused, as it cannot alter project state or cause unintended consequences.
From the tool's definition Tool name 'midi_get_note_names' and description 'Get MIDI note number to name mapping' indicate a retrieval operation that returns static reference data without modifying state or triggering external actions.
Documented attack patterns abuse exactly the kind of access midi_get_note_names gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ReaperMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for midi_get_note_names:
{
"version": "1",
"default": "deny",
"tools": {
"midi_get_note_names": {}
}
}midi_get_note_names is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get MIDI note number to name mapping (C4=60, etc.). It is categorised as a Read tool in the ReaperMCP MCP Server, which means it retrieves data without modifying state.
Register the Reaper MCP server in PolicyLayer and add a rule for midi_get_note_names: 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 ReaperMCP. Nothing to install.
midi_get_note_names is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the midi_get_note_names 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 midi_get_note_names. 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.
midi_get_note_names is provided by the Reaper MCP server (xdarkzx/reaper-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ReaperMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
138 ReaperMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.