wait_until_complete · Ai Mcp Terminal MCP: Risk & Policy

WHAT IT DOES

What wait_until_complete does on Ai Mcp Terminal

AI agents invoke wait_until_complete to trigger actions in Ai Mcp Terminal. 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_until_complete needs a policy

This tool orchestrates command execution workflows on a terminal management system. While it doesn't directly execute commands (that's done by siblings like execute_command), it controls the flow and completion of executed operations. This remains in the Execute category because it manages the lifecycle of potentially dangerous operations running on up to 100 concurrent terminals.

From the tool's definition Tool is part of a terminal management MCP server with sibling tools like 'execute_command', 'execute_batch', and 'broadcast_command'. The server description explicitly mentions 'async command execution' and 'real-time web monitoring'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_until_complete Rate-limited

wait_until_complete 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_until_complete": {
      "limits": [
        {
          "counter": "wait_until_complete_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 Ai Mcp Terminal, so you can run agents against it safely.

FAQ

Questions about wait_until_complete

What does the wait_until_complete tool do? +

wait_until_complete. It is categorised as a Execute tool in the Ai Mcp Terminal 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_until_complete? +

Register the Ai Mcp Terminal MCP server in PolicyLayer and add a rule for wait_until_complete: 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 Ai Mcp Terminal. Nothing to install.

What risk level is wait_until_complete? +

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

Can I rate-limit wait_until_complete? +

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

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

wait_until_complete is provided by the Ai Mcp Terminal MCP server (kanniganfan/ai-mcp-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.