Home Blog GCC
GCC

Agentic AI governance for Gulf teams: what is official, what is not, and what to build anyway

There is a lot of confident writing about Gulf AI rules. Here is what the official sources actually say, what is still unclear and a practical oversight design that does not depend on the answer.

By The Cadrix team6 min read
The Abu Dhabi skyline across turquoise water from a sandy beach
Photo by Nick Fewings on Unsplash

This is a practical note by a software team, not legal advice. Rules in the Gulf region change and differ by country, emirate and free zone. Check the official sources linked below, and ask a local lawyer before you rely on any of it.

If you search for "UAE agentic AI governance framework" you will find a lot of confident summaries. Some of them blur together three different things. Separating them is the useful part.

Thing one: the UAE government's own programme#

On 23 April 2026, the UAE Cabinet, chaired by Sheikh Mohammed bin Rashid Al Maktoum, announced a framework to move 50% of UAE government sectors and services to agentic AI within two years, described in the Government Media Office's account of the meeting as "Agentic AI for autonomous execution and decision-making". The Media Office text says implementation is overseen by Sheikh Mansour bin Zayed, driven by a task force chaired by Mohammad Al Gergawi, phased across ministries and federal entities, with expansion decided by performance and impact reviews, and with continuous AI training for federal employees. Officials are to be assessed on how well they adopt the change.

Read that carefully. It is a government transformation target for government services. It tells you the direction of travel and the level of political commitment. As described in the official text, it is not a rulebook that tells a private company how to run its own agents. We have not found language in it that creates obligations for businesses.

Thing two: a similarly named document from Singapore#

The title "Model AI Governance Framework for Agentic AI" belongs to Singapore. Singapore's Infocomm Media Development Authority launched it at Davos on 22 January 2026, building on its 2020 framework. Law-firm summaries describe four areas: assessing and bounding risks, making humans meaningfully accountable, technical controls, and end-user responsibility. The accountability area is described as defining checkpoints that need human approval, such as high-stakes or irreversible actions, and regularly auditing whether human oversight stays effective. A May 2026 update is reported as version 1.5 with case studies. Summaries describe it as guidance, not law.

We mention it because it is sometimes attributed to the UAE, and because it is the clearest published statement of how a government body thinks about oversight of agents. We read it through law-firm summaries and could not open IMDA's full document in preparation, so use the original for anything that matters.

Thing three: general law that already applies to your data#

Whatever you build, existing rules about personal data, sector regulation and contracts still apply. They vary: federal law, free-zone regimes such as DIFC and ADGM, and sector regulators each have their own. We are deliberately not summarising them here, because secondary sources disagree on the status of some implementing rules and we could not confirm them from official pages. If you handle personal data or operate in finance, health or government supply chains, this is the part to take to your counsel.

What this means in practice#

You can wait for clarity, or you can build oversight that holds up under most reasonable readings. We would build it, for two reasons. Your customers, auditors and boards will ask about it regardless of what is mandatory. It costs little to add early and a lot to retrofit.

Step 1: Sort workflows by what happens if they are wrong#

A simple scale works. Use three levels, and name an owner at each:

  • Assisting: the agent drafts or recommends, a person does the action. Low risk.
  • Supervised: the agent acts, but a person approves specific steps, or reviews a sample afterward.
  • Autonomous: the agent acts alone. Use only for low-risk, reversible work with good records.

Many teams describe these as people in the loop, on the loop and out of the loop. The names matter less than the discipline of deciding on purpose.

Step 2: Put approvals before irreversible actions#

The Singapore summaries single out high-stakes or irreversible actions as the natural checkpoints. That matches common sense: sending a message outside the company, changing a system of record, spending money, granting access. Put a person in front of those.

Step 3: Make oversight measurable#

Frameworks talk about auditing whether human oversight stays effective. A concrete way: for each approval step, track how often the answer is yes. If approvers accept 100% of requests, either the step is not needed, or nobody is reading.

Step 4: Keep the record#

You will want to show what the agent saw, what it proposed, who decided and what happened. Keep run history with step inputs and outputs, and keep approvals as part of the same record.

Step 5: Decide where the data goes#

For Gulf organisations this is often the first question. Where do documents get stored? Which model provider receives which content? Can the workflow run in a deployment you control? These are choices to make with your security and legal teams, before the first pilot.

How this looks in Cadrix#

Each of these steps maps to something you can configure:

  1. Workflows are built on a canvas, so the level of autonomy is visible: you can see where a human step sits.
  2. A Human Input step pauses the run until a person approves, edits or rejects. Runs waiting on someone show as Awaiting approval and in a Needs you queue.
  3. A Condition sends routine cases through and unusual ones to a person, using a threshold you set.
  4. Run history records each step with inputs, outputs and timing, and the approval is part of it. Retries create new linked runs.
  5. Roles and workspaces decide who can build, run and approve.
  6. For data location, speak to us about deployment options for your situation; we do not want to promise more here than a call can confirm.

Where the human goes. Choose the approver by role, with a backup, and make sure that person can read the request in the language the work is done in. For Arabic-language work, an approver who cannot read the Arabic source has no real oversight.

What we are not saying#

We are not saying that any specific regulation requires approval steps, or that this design makes you compliant. We have kept to what the official sources state and flagged what we could not confirm. The Saudi and wider GCC picture also deserves its own careful treatment from official publications, and we have left it out rather than repeat something we could not verify.

Sources#

Get new posts by email

Practical notes on governed AI workflows, in your inbox. Unsubscribe whenever you like.

Opens your email app to send the request. We use your address only to send the blog. See the privacy policy.

Keep reading