## Overview GitLab Duo will support configurable tool-level governance policies, giving group and project owners control over which agent actions are allowed, require human approval, or are blocked entirely. Today, once an agent is approved for a project, it can invoke any of its tools — including write and destructive operations — without any policy controls in place. This epic introduces the ability for owners to define rules at the group and project level that map each tool to one of three enforcement modes: - **Always Allow** — the tool executes without interruption - **Always Ask** — human approval is required before the tool executes - **Always Deny** — the tool is blocked entirely and invisible to the agent ## Problem Agents can execute high-risk actions — file deletions, bulk modifications, infrastructure changes — without any policy controls. There is currently no way to define which tools require approval or should be blocked, and no mechanism to enforce consistent governance policies across a group or project. ## What will be built - A Duo governance settings page at the group and project level where owners can configure tool rules, with cascading settings from group to project - A backend service to resolve which rule applies for a given tool invocation, with fail-closed defaults - GraphQL APIs to read and update tool rules - UI warnings in governance settings to surface configuration issues - Human-friendly tool names with descriptive tooltips in the governance UI - Clear denial messaging when a tool is blocked - Audit events when tool rules are created or updated ## Default behaviour Tools are classified into three action categories and ship with the following defaults: | Classification | Default mode | |---|---| | Read | Always Allow | | Write | Always Ask | | Delete | Always Ask | Group-level rules apply to all projects in the group unless overridden at the project level. Project-level rules can only be equal to or stricter than the group-level rule. ## Who can configure governance - **Group-level rules**: requires the Owner role for the top-level group - **Project-level rules**: requires the Maintainer or Owner role for the project ## Documentation https://docs.gitlab.com/user/duo_agent_platform/agents/tool-governance > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.