wait_for_stable · Poof MCP: Risk & Policy

WHAT IT DOES

What wait_for_stable does on Poof

AI agents invoke wait_for_stable to trigger actions in Poof. 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_for_stable needs a policy

While wait_for_stable appears passive (monitoring rather than directly executing commands), it is a critical enabler for Execute-category operations. It allows an AI agent to synchronize terminal automation workflows by waiting for command output to stabilize before proceeding. This is a coordination tool for multi-step command execution sequences.

From the tool's definition Tool enables monitoring of screen state on macOS Terminal.app via AppleScript, functioning as a synchronization mechanism for terminal control.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_for_stable Rate-limited

wait_for_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_for_stable": {
      "limits": [
        {
          "counter": "wait_for_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 Poof, so you can run agents against it safely.

FAQ

Questions about wait_for_stable

What does the wait_for_stable tool do? +

Wait for screen to stop changing (500ms stable duration). It is categorised as a Execute tool in the Poof 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_for_stable? +

Register the Poof MCP server in PolicyLayer and add a rule for wait_for_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 Poof. Nothing to install.

What risk level is wait_for_stable? +

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

Can I rate-limit wait_for_stable? +

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

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

wait_for_stable is provided by the Poof MCP server (mattapperson/poof-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.