Login Register
Granular Permissions: What AI Can and Cannot Do

Enabling and Disabling Individual Commands

Estimated reading: 0 minutes 8 views

GameCatalyst’s permission system lets you control exactly which commands your AI assistant can execute. Every command can be individually enabled or disabled, giving you complete control over what the AI can and cannot do.

How to enable or disable commands:

  1. Open the GameCatalyst Dashboard in Unity
  2. Click the Settings tab
  3. Click Tool Permissions in the left sidebar
  4. You’ll see a list of all 60+ commands organized by category
  5. Each command has a toggle switch next to it
  6. Click the toggle to enable (green) or disable (gray) a command

What happens when you disable a command:

When you disable a command, it immediately becomes unavailable to all connected AI clients. If an AI tries to use a disabled command, it receives a clear error message: “This command is not available. Check Tool Permissions in the Dashboard.”

The AI sees which commands are available through the get_available_tools management command. When you change permissions, the AI’s tool list updates within 5 seconds automatically. No need to restart anything.

Common use cases:

  • Disable file deletion — Turn off file.delete and folder.delete if you want the AI to create and modify files but never delete them
  • Disable play mode control — Turn off play_mode if you want to manually control when Unity enters play mode
  • Disable component modification — Turn off component.set if you want the AI to create objects but not modify existing components
  • Disable workspace.plan — Turn off the workspace.plan command if you prefer the AI to use its own planning system (DAP guidance still applies)

Permission inheritance:

GameCatalyst uses a 4-layer permission system. A command must be allowed at every layer to execute:

  1. Command Definitions — The command exists in the system
  2. Project Permissions — The project allows this command
  3. Engine Session — The Unity instance allows this command
  4. Client Session — The AI client’s session allows this command (intersection of all above)

When you toggle a command in the Dashboard, you’re controlling Layer 2 (Project Permissions). The change propagates through all layers automatically.

Manual refresh:

If permissions don’t seem to update, click the Update Permissions button at the bottom of the Tool Permissions tab. This forces an immediate refresh across all layers.

Share this Doc

Enabling and Disabling Individual Commands

Or copy link

CONTENTS
Antimanual

Ask our AI support assistant your questions about our platform, features, and services.

You are offline
Chatbot Avatar
What can I help you with?