get_notes
Get MIDI notes from a clip region. Returns note_id, pitch, start_time, duration, velocity, mute, probability.
This record as markdown: /tools/io-github-dreamrec-livepilot/get-notes.md
What get_notes does on Livepilot
AI agents call get_notes to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_notes is rated Low
This tool retrieves and queries MIDI note data from Ableton Live without side effects. It does not create, modify, delete, or execute any operations — it only fetches metadata about existing notes. This is a classic Read operation with minimal risk even if called repeatedly or with unexpected arguments.
From the tool's definition Tool name 'get_notes' and description explicitly states it 'Get[s] MIDI notes from a clip region' and 'Returns note_id, pitch, start_time, duration, velocity, mute, probability' — a read-only retrieval of existing data with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs get_notes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_notes, this is the rule to start with:
get_notes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every get_notes call is checked against it from then on.
Questions about get_notes
Get MIDI notes from a clip region. Returns note_id, pitch, start_time, duration, velocity, mute, probability. It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for get_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 Livepilot. Nothing to install.
get_notes 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 get_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 get_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.
get_notes is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue