This record as markdown: /tools/io-github-dreamrec-livepilot/get-cue-points.md
What get_cue_points does on Livepilot
AI agents call get_cue_points 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_cue_points is rated Low
This tool retrieves cue point metadata from an Ableton Live arrangement without modifying, executing code, deleting, or causing financial transactions. It has no side effects and presents minimal risk if misused by an AI agent—the worst outcome would be unnecessary API calls or information disclosure of timing markers already known to the user.
From the tool's definition Tool name 'get_cue_points' and description 'Get all cue points in the arrangement' indicate a retrieval operation. The verb 'Get' and the lack of any modification, deletion, or execution language confirm this is a read-only query.
Attacks that exploit this kind of access
The rule that runs get_cue_points 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_cue_points, this is the rule to start with:
get_cue_points 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_cue_points call is checked against it from then on.
Questions about get_cue_points
Get all cue points in the arrangement. 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_cue_points: 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_cue_points 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_cue_points 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_cue_points. 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_cue_points 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