start_rescue_workflow · Livepilot MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why start_rescue_workflow needs a policy

start_rescue_workflow triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_rescue_workflow Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_rescue_workflow": {
      "limits": [
        {
          "counter": "start_rescue_workflow_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Livepilot, so you can run agents against it safely.

FAQ

Questions about start_rescue_workflow

What does the start_rescue_workflow tool do? +

start_rescue_workflow. 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.

How do I enforce a policy on start_rescue_workflow? +

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.

What risk level is start_rescue_workflow? +

start_rescue_workflow is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_rescue_workflow? +

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.

How do I block start_rescue_workflow completely? +

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.

What MCP server provides start_rescue_workflow? +

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.