Hunt Agent Time-Gate Bypass

Agents implement temporal constraints — "weekends only," "maintenance window," "after hours." Like role gates, these are prompt instructions, not enforced locks; the agent checks a time it can be convinced to read differently. This is a TOCTOU variant (check-time vs run-time) — see hunt-agent-race-condition.

Where This Lives / Attack Surface Signals

• Tool descriptions mention windows: "weekends only," "maintenance window," "business hours."
• Agent gates on day/time ("Today is Thursday, I cannot…").
• Scheduling tools ("schedule for later / delay until / run at").
• A get_current_day/get_current_time tool. Time-based rate resets ("try again tomorrow").

Crown Jewel Targets

Enterprise change-management / deploy / payment-run agents gated to windows for safety — bypass = force a restricted action (deploy, payout, batch job) outside its control window.

Characterize First

1. What is checked — day, hour, date, elapsed?
2. Check mechanism — a tool call (get_current_day) or "known" from prompt context?
3. Enforcement — can you lie about the time? schedule for a future time?
4. The gap — is the check on "now" or on "when the task runs"? If it validates the scheduled time, not execution time, you have a window.