Directory / Grok Bot
Grok Bot
Runs on a per-user hosted computer. Local-computer commands need approval by default, but a review model decides hosted actions. Network allowlists, audit logs, action recording and admin locks are Enterprise only.
Disclosure: this listing was researched and drafted with Grok Bot, the product being rated. Each control was re-checked against Grok Bot's public docs by a separate review pass, and corrections are welcome.
Lock this down first
On Enterprise, enforce Auto-review, set a Team Allowlist network policy, and set Execution on Local Computer to Never allow.
Scorecard
| Criterion | Rating | Notes |
|---|---|---|
| Permission granularity | 2/3 | Personal and admin Auto-review rules; admin rules are locked for members, and admins can cap local execution (Enterprise only). Rules are judged by a review model, not enforced deterministically. |
| Human approval gates | 1/3 | Local commands ask every time by default, but hosted actions, most of the work, go to an Auto Review model that can proceed, require approval or deny. |
| Sandboxing | 2/3 | Each member gets a separate hosted computer. Per-user isolation, not a per-command sandbox. |
| Secrets handling | 2/3 | Connector tokens stay on the backend and never reach the computer, and secure secret requests keep values away from the model. Files and browser sessions persist on the computer's disk. |
| Audit logs | 2/3 | Audit logs (admin events) and Action Recording (bot actions, 90 days) are Enterprise only. Action Recording is off by default. |
| Kill switch / interrupt | 1/3 | Only Enterprise admins can terminate a member's computer, which stops running Bots. No member-level stop control is documented on the cited pages. |
| Network egress control | 2/3 | Off by default: teams without a policy allow all. Enterprise admins can set an allowlist-only network policy. |
Sources
Vendor? Request a correction. We review corrections within 7 days.