AI agents call find_midi_notes_by_pitch to retrieve information from Reaper Reapy without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries or retrieves data about MIDI notes based on pitch without modifying state. It does not create, modify, delete, execute code, or commit financial obligations. Despite the empty description introducing some ambiguity, the 'find' naming pattern and context of other tools on the server strongly indicate a read-only data retrieval capability.
From the tool's definition Tool name 'find_midi_notes_by_pitch' indicates a query/search operation that retrieves MIDI notes matching a specified pitch criterion.
Documented attack patterns abuse exactly the kind of access find_midi_notes_by_pitch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reaper Reapy, and nothing reaches the server without passing your rules. This is the rule we recommend for find_midi_notes_by_pitch:
{
"version": "1",
"default": "deny",
"tools": {
"find_midi_notes_by_pitch": {}
}
}find_midi_notes_by_pitch 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.
find_midi_notes_by_pitch. It is categorised as a Read tool in the Reaper Reapy MCP Server, which means it retrieves data without modifying state.
Register the Reaper Reapy MCP server in PolicyLayer and add a rule for find_midi_notes_by_pitch: 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 Reaper Reapy. Nothing to install.
find_midi_notes_by_pitch 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 find_midi_notes_by_pitch 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 find_midi_notes_by_pitch. 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.
find_midi_notes_by_pitch is provided by the Reaper Reapy MCP server (wegitor/reaper-reapy-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 47 Reaper Reapy tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
47 Reaper Reapy tools catalogued and risk-classified — across an index of 42,500+ MCP servers.