Configure Ocelot Guardrails

Use this guide when

Use this page when you are an owner or admin and need to decide what Ocelot is allowed to do in an organization.

Confirm access first

You need:

• owner or admin access
• an active subscription on the organization

If either requirement is missing, Ocelot settings will not be available.

Step 1: Review current usage

Open Ocelot Settings and check the usage cards first. They show current daily usage and plan limits for:

• AI queries
• tool actions
• image analyses
• saved notes

This tells you whether the problem is policy, permissions, or simple usage exhaustion.

Step 2: Set the allowed tool groups

Choose the smallest tool surface that still supports your team's work.

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 toggles define Ocelot's blast radius for that organization.

Step 3: Set the safety controls

The three controls that matter most are:

• YOLO Mode, which removes normal approval boundaries
• Emergency Stop, which blocks Ocelot activity immediately
• Daily AI Hard Limit, which sets an organization-specific circuit breaker below the plan maximum if needed

Step 4: Review shared notes

Ocelot can keep workspace notes for future sessions. Use the notes section to:

• search saved notes
• review stored content
• delete notes that no longer belong in the workspace

Recommended default

For most teams, a safe starting point is:

• leave Ocelot enabled
• allow read-oriented tools first
• keep approval boundaries on
• leave YOLO Mode off
• use emergency stop only as a temporary block

Related pages

• Use Ocelot
• Access Model