Configure AI developer tools settings

Use the AI developer tools settings page in Gemini Enterprise to configure developer tools, enforce security and compliance controls, and manage model availability for your organization.

Before you begin

Make sure you have the following:

  • Invoiced Cloud Billing account: To use AI developer tools, your project must have Cloud Billing enabled. AI developer tools are available for invoiced accounts only. For more information, see Cloud Billing account types.

  • Supported editions: To access AI developer tools, users must have a subscription to the Gemini Enterprise Standard, Plus, or Pay-as-you-go edition.

  • Supported regions: For more information about regional availability and feature limitations, see Data residency for Gemini Enterprise Standard and Plus Editions and Gemini Notebook.

  • Required APIs: Your project must have the following APIs enabled:

    • Gemini Enterprise API (discoveryengine.googleapis.com)
    • Business AI Code API (businessaicode.googleapis.com)

    When you turn on the AI developer tools toggle in the Google Cloud console, the system checks your project configuration and automatically enables these required APIs if you haven't already enabled them.

Turn on AI developer tools

The availability of AI developer tools depends on your Gemini Enterprise subscription type:

  • New Standard, Plus, or Pay-as-you-go subscriptions: AI developer tools is enabled by default in the location where you purchased the subscription if it is supported for that location or region.

  • Existing subscriptions: An administrator must manually enable AI developer tools in the Google Cloud console for each location to activate the tools for licensed users.

To manually enable AI developer tools for an existing Gemini Enterprise subscription, follow these steps:

  1. In the Google Cloud console, go to Gemini Enterprise.

    Gemini Enterprise

  2. Click Settings, and select the AI developer tools tab.

  3. Turn on the AI developer tools toggle.

  4. Configure the settings in the Security, Compliance, and Model availability sections.

Configure security settings

As an administrator, you can prevent unauthorized data exposure across developer interfaces. Use the settings in this section to restrict access to external sources and manage automated execution permissions. For example, you can enforce mandatory security policies to prevent users from overriding safety rules, and require approval before AI agents run terminal commands or select links.

Manage security policies

You can configure security policies to control how AI agents access local files outside their working folders and execute terminal commands in developer workspaces.

Setting Description Default status
Outside of file access policy Specify the agent's permission level for accessing files outside of its designated working folders. The following options are available:
  • Deny: Prevents the agent from accessing files outside its working folders.
  • Always ask: Prompts the user for permission before the agent accesses files outside its working folders.
  • Allow: Permits the agent to access files outside its working folders without prompting.
 Deny
Terminal auto-execution mode Enable this setting to let agents run terminal commands automatically to streamline multi-step workflows. The following options are available:
  • Require review: Prompts the user for approval before running any terminal command.
  • Proceed in sandbox: Automatically runs commands in a secure, isolated environment.
  • Always proceed: Automatically runs commands in the current environment without prompting.
 Always proceed
Sandbox mode Enable this setting to restrict agent tools to a secure, isolated local sandbox. Disabled

Manage external web access

If your security policy requires controlling agent access to external websites to prevent data exfiltration, these settings let you limit browser access or restrict it to a list of allowed URLs.

Setting Description Default status
Browser access Enable this setting to control external web access. This prevents data exfiltration and defines organizational boundaries. Disabled
Allowed URLs Enable this setting to specify a list of allowed URLs. When configured, the system blocks all other URLs. None. By default, no URLs are blocked.
Browser JavaScript auto-execution mode Enable this setting to let agents run JavaScript to support advanced web-based coding and testing tasks. The following options are available:
  • Disabled: Prevents the agent from running JavaScript.
  • Request review: Prompts the user for approval before the agent runs JavaScript.
  • Allowed: Permits the agent to run JavaScript automatically.
 Disabled

Manage Model Context Protocol (MCP)

You can configure access to Model Context Protocol (MCP) servers, which lets AI agents securely access additional data sources and tools.

Setting Description Default status
MCP servers (preview) Enable this setting to manage access to Model Context Protocol (MCP) servers to securely extend the AI's data context. Disabled
Allowed server configuration This setting lets you define specific server configurations for MCP access. Administrators define the allowlist as a JSON object, and the UI provides real-time validation for the following fields:
  • url: (string) the endpoint of the MCP server.
  • type: (string) the transport protocol, either sse or http.
  • trust: (boolean) whether the client should treat this server as trusted.
  • includeTools: (array of strings) tools to be explicitly allowed from this server.
  • excludeTools: (array of strings) tools to be explicitly disallowed from this server.

Example configuration

{
  "mcpServers": {
    "external-provider": {
      "url": "https://external.mcp-provider.com",
      "type": "sse",
      "trust": true,
      "includeTools": ["writeTool", "capacityTool"],
      "excludeTools": []
    },
    "internal-corp-tool": {
      "url": "https://mcp.internal-tool.corp",
      "type": "http",
      "includeTools": [],
      "excludeTools": ["adminTool"]
    }
  }
}
Not configured

Configure compliance settings

If your organization operates in a regulated industry or has specific internal policies, you might need to maintain audit logs of AI interactions for compliance. This section's settings let you configure logging and data retention policies to meet your legal and regulatory requirements.

Setting Description Default status
Prompts and responses logging Enable this setting to record interactions between developers and the AI to compute usage metrics and maintain an audit trail for security reviews. The system stores logs securely within your organization's project, and Google never accesses the logs for model training or human review. Disabled
Metadata logging Enable this setting to record product metadata to help you track usage and analytics across your organization. The system stores logs securely within your organization's project, and Google never accesses the logs for model training or human review. Disabled

Configure model availability

Use the settings in this section to authorize specific AI models and manage access levels. This ensures developers only use AI models that comply with your organization's safety and usage policies. For example, you can give developers access to preview models for experiments, or restrict tools to use only authorized models.

Setting Description Default status
Antigravity authorized models Enable this setting to specify which AI models the Antigravity tool is authorized to use within the project. Only models made by Google are available in Gemini Enterprise AI developer tools. For more information about supported models, see the Enterprise column in the list of supported models.