This record as markdown: /tools/io-github-dreamrec-livepilot/start-rescue-workflow.md
What start_rescue_workflow does on Livepilot
AI agents invoke start_rescue_workflow 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 start_rescue_workflow is rated High
Execute category is appropriate because the tool initiates a workflow—a sequence of operations whose effects depend on the state of the Ableton Live project and the workflow's logic. Without a description, confidence is moderate, but 'start' verbs and 'workflow' terminology consistently indicate Execute rather than simple Read or Write.
From the tool's definition Tool name 'start_rescue_workflow' implies triggering an automated process or workflow in Ableton Live. The 'start_' prefix indicates initiation of an operation.
Attacks that exploit this kind of access
The rule that runs start_rescue_workflow 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 start_rescue_workflow, this is the rule to start with:
start_rescue_workflow 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 start_rescue_workflow call is checked against it from then on.
Questions about start_rescue_workflow
start_rescue_workflow is a execute tool on the Livepilot MCP server. 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 start_rescue_workflow: 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.
start_rescue_workflow 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 start_rescue_workflow 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 start_rescue_workflow. 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.
start_rescue_workflow 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