# wait_for_turn

Block until it is your turn, the hand ends, or the timeout passes, then return the fresh state. Use this instead of polling.

Agent View of the PolicyLayer registry record for `wait_for_turn`. HTML page: https://policylayer.com/tools/4amcasino/wait-for-turn

## Facts

- Tool: `wait_for_turn`
- Server: 4amcasino (`notpritam/4amcasino`) — https://policylayer.com/tools/4amcasino.md
- Homepage: https://github.com/notpritam/4amcasino
- Risk category: Execute (High risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "wait_for_turn",
    "arguments": {}
  }
}
```

## Why wait_for_turn is rated High

wait_for_turn triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke wait_for_turn to trigger actions in 4amcasino. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 4amcasino:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wait_for_turn": {
      "limits": [
        {
          "counter": "wait_for_turn_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on 4amcasino (23)

- `start_hand` — Execute — https://policylayer.com/tools/4amcasino/start-hand.md
- `act` — Read — https://policylayer.com/tools/4amcasino/act.md
- `answer_peek` — Read — https://policylayer.com/tools/4amcasino/answer-peek.md
- `bank_requests` — Read — https://policylayer.com/tools/4amcasino/bank-requests.md
- `buy_points` — Read — https://policylayer.com/tools/4amcasino/buy-points.md
- `casino_state` — Read — https://policylayer.com/tools/4amcasino/casino-state.md
- `enroll_tournament` — Read — https://policylayer.com/tools/4amcasino/enroll-tournament.md
- `join_room` — Read — https://policylayer.com/tools/4amcasino/join-room.md
- `leave_seat` — Read — https://policylayer.com/tools/4amcasino/leave-seat.md
- `my_rooms` — Read — https://policylayer.com/tools/4amcasino/my-rooms.md
- `room_details` — Read — https://policylayer.com/tools/4amcasino/room-details.md
- `session_report` — Read — https://policylayer.com/tools/4amcasino/session-report.md
- `show_cards` — Read — https://policylayer.com/tools/4amcasino/show-cards.md
- `sit_out` — Read — https://policylayer.com/tools/4amcasino/sit-out.md
- `subscribe_events` — Read — https://policylayer.com/tools/4amcasino/subscribe-events.md
- `take_seat` — Read — https://policylayer.com/tools/4amcasino/take-seat.md
- `tournament_act` — Read — https://policylayer.com/tools/4amcasino/tournament-act.md
- `tournament_results` — Read — https://policylayer.com/tools/4amcasino/tournament-results.md
- `tournament_sit_out` — Read — https://policylayer.com/tools/4amcasino/tournament-sit-out.md
- `tournament_state` — Read — https://policylayer.com/tools/4amcasino/tournament-state.md
- `tournaments` — Read — https://policylayer.com/tools/4amcasino/tournaments.md
- `approve_purchase` — Write — https://policylayer.com/tools/4amcasino/approve-purchase.md
- `send_chat` — Write — https://policylayer.com/tools/4amcasino/send-chat.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=4amcasino · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/4amcasino