wait · Claude DJ MCP: Risk & Policy

WHAT IT DOES

What wait does on Claude DJ MCP

AI agents invoke wait to trigger actions in Claude DJ MCP. 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 needs a policy

The tool triggers execution logic (waiting, event polling, request retrieval) as part of an autonomous DJ system's control flow. While it has no destructive or financial consequences, it actively executes a timed operation and state transition. The low severity reflects that misuse primarily affects music playback timing rather than data integrity or system damage.

From the tool's definition Tool description states it 'Wait[s] for a specified number of seconds' and controls timing behavior in the 'core DJ loop'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wait Rate-limited

wait 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": {
      "limits": [
        {
          "counter": "wait_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 DJ MCP, so you can run agents against it safely.

FAQ

Questions about wait

What does the wait tool do? +

Wait for a specified number of seconds (letting the music play), then return any pending user requests. This is the core DJ loop tool. It is categorised as a Execute tool in the Claude DJ MCP 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? +

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

What risk level is wait? +

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

Can I rate-limit wait? +

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

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

wait is provided by the Claude DJ MCP server (uetuluk/claude-dj-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.