spawn_pilot_agent · Helix Pilot MCP: Risk & Policy

WHAT IT DOES

What spawn_pilot_agent does on Helix Pilot

AI agents invoke spawn_pilot_agent to trigger actions in Helix Pilot. 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 spawn_pilot_agent needs a policy

spawn_pilot_agent 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

spawn_pilot_agent Rate-limited

spawn_pilot_agent 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": {
    "spawn_pilot_agent": {
      "limits": [
        {
          "counter": "spawn_pilot_agent_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 Helix Pilot, so you can run agents against it safely.

FAQ

Questions about spawn_pilot_agent

What does the spawn_pilot_agent tool do? +

Start a background helix-pilot agent for auto or browse workflows. It is categorised as a Execute tool in the Helix Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on spawn_pilot_agent? +

Register the Helix Pilot MCP server in PolicyLayer and add a rule for spawn_pilot_agent: 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 Helix Pilot. Nothing to install.

What risk level is spawn_pilot_agent? +

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

Can I rate-limit spawn_pilot_agent? +

Yes. Add a rate_limit block to the spawn_pilot_agent 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 spawn_pilot_agent completely? +

Set action: deny in the PolicyLayer policy for spawn_pilot_agent. 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 spawn_pilot_agent? +

spawn_pilot_agent is provided by the Helix Pilot MCP server (tsunamayo7/helix-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.