vibekit_wait_for_task · Vibekit MCP: Risk & Policy

WHAT IT DOES

What vibekit_wait_for_task does on Vibekit

AI agents invoke vibekit_wait_for_task to trigger actions in Vibekit. 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 vibekit_wait_for_task needs a policy

This tool blocks until a task completes, indicating it supervises arbitrary task execution. While the tool itself does not directly execute code, it is part of an execution pipeline (vibekit_agent_* tools, database operations) where an AI agent could submit arbitrary tasks and wait for results. The polling mechanism suggests dependency on external state changes from task execution.

From the tool's definition Tool waits for task completion via polling ('polling every 5 seconds'), implying it monitors and depends on task execution outcomes.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vibekit_wait_for_task Rate-limited

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

FAQ

Questions about vibekit_wait_for_task

What does the vibekit_wait_for_task tool do? +

Wait for a task to complete, polling every 5 seconds. It is categorised as a Execute tool in the Vibekit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vibekit_wait_for_task? +

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

What risk level is vibekit_wait_for_task? +

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

Can I rate-limit vibekit_wait_for_task? +

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

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

vibekit_wait_for_task is provided by the Vibekit MCP server (vibekit-apps/vibekit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.