This record as markdown: /tools/io-github-dreamrec-livepilot/jump-to-cue.md
What jump_to_cue does on Livepilot
AI agents invoke jump_to_cue to trigger actions in Livepilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why jump_to_cue is rated High
This tool executes a playback navigation action in Ableton Live, moving the playhead to a specific cue point. It doesn't read data passively, nor does it write/modify persistent data or destroy anything. It triggers an external operation (transport jump) in the DAW, making Execute the best fit. Severity is low as misuse would only disrupt playback position.
From the tool's definition 'Jump to a cue point by index' — triggers a transport/playback position change in Ableton Live
Attacks that exploit this kind of access
The rule that runs jump_to_cue 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 jump_to_cue, this is the rule to start with:
jump_to_cue stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 jump_to_cue call is checked against it from then on.
Questions about jump_to_cue
Jump to a cue point by index. It is categorised as a Execute tool in the Livepilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Livepilot MCP server in PolicyLayer and add a rule for jump_to_cue: 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.
jump_to_cue is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jump_to_cue 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 jump_to_cue. 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.
jump_to_cue 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.
Across the catalogue