wait_dispatch · Claude Bridge MCP: Risk & Policy

WHAT IT DOES

What wait_dispatch does on Claude Bridge

AI agents invoke wait_dispatch to trigger actions in Claude Bridge. 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_dispatch needs a policy

The tool's name 'wait_dispatch' combined with its position among dispatch-related tools suggests it blocks/waits for results from previously dispatched work (via 'dispatch' or 'dispatch_async'). Since the server explicitly executes arbitrary 'work' and 'Claude Code' in a devcontainer, waiting on such results constitutes triggering/observing the effects of external code execution. This is Execute-category behavior.

From the tool's definition Tool is part of a server that 'dispatch[es] work into Claude Code running inside your devcontainer' with sibling tools named 'dispatch', 'dispatch_async', and 'get_dispatch', indicating this tool waits for execution results from arbitrary code running in a…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait_dispatch Rate-limited

wait_dispatch 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_dispatch": {
      "limits": [
        {
          "counter": "wait_dispatch_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 Claude Bridge, so you can run agents against it safely.

FAQ

Questions about wait_dispatch

What does the wait_dispatch tool do? +

wait_dispatch. It is categorised as a Execute tool in the Claude Bridge 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_dispatch? +

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

What risk level is wait_dispatch? +

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

Can I rate-limit wait_dispatch? +

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

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

wait_dispatch is provided by the Claude Bridge MCP server (josiahsiegel/claude-bridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.