Configure Ocelot Guardrails
Control Ocelot access, approvals, usage limits, and saved notes.
Use this guide when
Use this guide to control what Ocelot can do for your organization.
Make sure that you have access
You need:
- owner or admin access
- an organization plan that includes the Ocelot features you need
Only owners and admins can open this page. The organization plan sets the usage limits and available tool groups.
Step 1: Review current usage
Open Ocelot under Manage in the organization sidebar. Review the usage cards for these limits:
- AI queries
- tool actions
- image analyses
- saved notes
These cards show whether a rule, permission, or usage limit blocked Ocelot.
Step 2: Set the allowed tool groups
Enable only the tool groups that your team needs.
Tool groups include:
- console access
- files
- players
- commands
- web access
- databases
- shell access
- processes
- containers
- services
- events
- plugins
- permissions
- economy
- player-admin actions
- server lifecycle actions
These settings control the actions that Ocelot can perform.
Step 3: Set the safety controls
Set these controls:
- YOLO Mode removes approval prompts for allowed tools.
- Emergency Stop blocks Ocelot immediately.
- Daily AI Hard Limit sets a daily limit that can be lower than the plan limit.
Keep YOLO Mode off by default
CAUTION: Leave YOLO Mode off for normal team use. This mode removes approval prompts for allowed tools. Permissions, plan limits, disabled tool groups, and Emergency Stop still apply.
Step 4: Review shared notes
Ocelot can save workspace notes for later sessions. In the notes section, you can:
- search saved notes
- review stored content
- remove notes that your team no longer needs
Recommended default
Start with this configuration:
- leave Ocelot enabled
- start with read-only tools
- keep approval prompts enabled
- leave YOLO Mode off
- use Emergency Stop only as a temporary block
Related pages
Was this page helpful?
Send a quick note if anything is missing or unclear.
Last updated on