wait_stable · Helix Pilot MCP: Risk & Policy

WHAT IT DOES

What wait_stable does on Helix Pilot

AI agents invoke wait_stable 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 wait_stable needs a policy

wait_stable 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

wait_stable Rate-limited

wait_stable 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": {
    "wait_stable": {
      "limits": [
        {
          "counter": "wait_stable_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 wait_stable

What does the wait_stable tool do? +

Wait until the screen content stabilizes. 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 wait_stable? +

Register the Helix Pilot MCP server in PolicyLayer and add a rule for wait_stable: 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 wait_stable? +

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

Can I rate-limit wait_stable? +

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

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

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