Skip to content
NEWWhich kind of AI user are you?
Take the two-minute check
AIAC AI ASSURANCE COUNCIL™

Agentic AI oversight

MAS Consultation Paper P017-2025 — Consultation Paper on Guidelines on Artificial Intelligence Risk Management

MAS has not issued guidelines on AI risk management. It has consulted on them. Consultation Paper P017-2025 closed on 31 January 2026, and the draft Guidelines at its section 6 remain a draft, with a twelve-month transition proposed rather than granted. Nothing in them applies to any financial institution today, and the agentic content is four paragraphs.

§ 1 — Who it binds

Who it would reach, if issued

Deployer

Nothing today: the instrument is a draft and binds nobody. If issued as consulted on, it would reach financial institutions as defined in the Financial Services and Markets Act 2022, in three tiers — basic policies for all, oversight and systems for those using AI as an integrated part of business processes, and lifecycle controls by relevance and risk materiality. The draft does not use provider or deployer language at all; it reaches an institution because of what it is.

§ 2 — In practice

A draft, two numbering schemes, and no agentic chapter

Establish what the document is before citing anything from it. MAS published Consultation Paper P017-2025, *Consultation Paper on Guidelines on Artificial Intelligence Risk Management*, in November 2025; the consultation closed on 31 January 2026; the Guidelines are not finalised. MAS’s written reply to a parliamentary question for the sitting of 5 August 2026 says they apply to all AI use cases by financial institutions, agentic AI included, and will be finalised soon. The paper proposes a twelve-month transition following issuance, which is a proposal and not a grant. So the verbs matter: MAS proposes, the draft Guidelines state. There is a second trap in the citation itself. The document carries two numbering schemes — the consultation paper’s own paragraphs, and the draft Guidelines at section 6, which restart at 1 and run through their own numbering to an Annex. A bare "paragraph 4.10" is therefore ambiguous: in the draft Guidelines it is the human-oversight paragraph, while the consultation paper’s 4.7 is the transition proposal. Secondary commentary conflates the two routinely, and a page inheriting that error cites a paragraph saying something else.

There is no agentic chapter, and institutions looking for one conclude that MAS has not addressed agents. The draft Guidelines name them in four places — paragraph 1.3, stating that the expectations apply as institutions deploy AI and AI technologies including generative AI and newer developments such as AI agents; paragraph 1.10; paragraph 4.15, asking that evaluation and testing of newer developments cover their key failure modes; and a footnote to paragraph 4.12 on third-party agents — plus autonomy at paragraph 3.10(c). Only 1.10 is substantive, and it is worth reading as written: an AI agent with access to tools could autonomously execute actions not aligned with an institution’s business objectives or a customer’s best interests, through a divergence between human goals and how the agent translated those goals into actions; and compromised agents with access to internal systems and external tools could exfiltrate sensitive data or execute malicious commands at scale. An institution cannot scope an agentic gap analysis by searching the text for *agent*. The whole of section 4 applies.

The proposal with the most consequence for an agentic deployment sits in none of those paragraphs. Draft Guidelines paragraph 3.10(c) puts *Reliance* into the risk-materiality assessment as a dimension it must minimally cover — the level of autonomy granted to the system or model, the degree of human involvement or oversight in the process it supports, and the availability of alternatives. Risk materiality then drives everything downstream: how intensively lifecycle controls apply, whether formal independent validation is required before deployment, how often re-validation happens, how closely the system is monitored. Under the draft, raising an agent’s autonomy is a change to its supervisory classification. Very few institutions run a materiality methodology in which autonomy is a scored input, and the test is blunt — score a use case, raise its autonomy, and see whether the number moves. Where it does not, the methodology does not implement 3.10(c) whatever the policy says it does.

Two structural proposals are widely read as one rule each when they are two. Validation is tiered. High risk materiality would get formal independent validation before deployment, by people with the necessary expertise and objectivity who are independent of the development and deployment teams and able to provide effective challenge, covering conceptual soundness, data inputs, implementation integrity, evaluation measures and thresholds, explainability and fairness, and assumptions and limitations — the evidence side of which is set out under stress testing agentic systems. Everything else would get documented review of another kind, such as peer review by qualified individuals not involved in development or deployment — and a footnote closes the obvious gap by extending "not involved" to ongoing deployment as well. The proportionality floor is also lower than firms expect: every institution, without qualification, would hold basic policies naming a senior-management responsible person. The Annex examples of AI *integrated as part of business processes* are unglamorous — an internal helpdesk chatbot, document data extraction — and turn on a dependency test rather than a risk one, so a productivity tool nobody governs may cross the line.

Two orientation points close this out. The draft is not framed in provider and deployer terms at all, which is genuine friction with the Union vocabulary rather than something to paper over: it catches an institution for what it is, where the EU regime catches a system for what it does. A credit-scoring agent is inside the high-risk perimeter through Article 6 and Annex III whoever runs it, and would be inside the MAS perimeter because a regulated institution runs it, whatever it does. A firm subject to both is scoping against two gateways over an overlapping population, and the deeming provisions that partly reconcile them are set out on the Article 26 page. Second, the draft points to the IMDA agentic framework, at its own footnote 3 and at paragraph 2.7 of the consultation paper: the two Singapore instruments are meant to be read together, so the envelope work in bounding an agent’s authority is not a separate exercise from this one.

§ 3 — What a weak answer looks like

The gap analysis done with a search box

The gap analysis performed by searching the draft for the word "agent". It returns four hits, the conclusion is that MAS has not really addressed agents yet, and the work is deferred until the Guidelines are final. Both halves fail. The agentic content is deliberately embedded rather than sectioned off, so the whole lifecycle chapter applies to an agent and the searchable paragraphs are the least of it. And waiting for finalisation skips the one thing that takes longest to build — a materiality methodology in which autonomy is a scored input, without which every downstream intensity setting is derived from a classification that cannot see what the system now does.

§ 4 — What discharges it

What an institution would have to evidence

The artefacts an assessor asks to see, and what makes each one sufficient rather than merely present.

  1. 01

    An AI inventory with agentic dependencies populated

    For an agent, dependencies have to reach tools, protocol servers and other agents. An inventory whose schema predates agents cannot hold that, which is why the draft asks for the inventory design itself to be reviewed.

  2. 02

    A risk-materiality methodology in which autonomy scores

    Worked assessments showing an agentic use case landing differently from a comparable non-agentic one. If raising autonomy does not move the number, the Reliance dimension has been written into the policy and not into the method.

  3. 03

    An independent validation report for one agentic use case

    Traceable across all six areas the draft names, with the validator’s reporting line visible and the effective-challenge exchange preserved. A report agreeing with the build team throughout evidences agreement, not challenge.

  4. 04

    The identification function’s decision log of borderline cases

    Agents arrive inside purchased products without announcement, so the interesting record is the marginal calls: what was judged in scope, what was not, and who arbitrated. A log with no borderline entries suggests nobody is looking at the margin.

  5. 05

    Contract terms on notification before a product turns agentic

    The right to audit, notification when AI is introduced, or the institution’s agreement before it is incorporated. The notification clause is the one to look for; agreements signed before 2025 almost never carry it.

  6. 06

    A tested kill switch, timed, with the resulting state recorded

    Elapsed time to full deactivation including sub-agents and third-party integrations, and what condition the business was left in. Deactivation is not recovery, and the dependencies exposed by stopping are the point of the drill.

§ 5 — Worked example

Worked example — the platform that turned agentic at a release

A Singapore-licensed insurer uses a claims administration platform from a vendor. At a quarterly release the vendor enables an assistant that reads claim documents, drafts adjuster notes and, where a claim falls under a threshold, prepares the settlement for one-click approval. Nobody told the insurer in advance. The platform is on the AI inventory as a workflow tool with no AI attributes recorded, and its risk materiality was scored two years ago as low.

Under the draft Guidelines, what has changed and what should have caught it?

Three things changed at once and none of them went through a control. The system acquired autonomy and tool access, which under the Reliance dimension is an input to risk materiality — so the two-year-old low score is stale by the draft’s own logic, and every downstream intensity setting inherited from it is stale too. The inventory is wrong in a way its schema causes: an entry describing a workflow tool has nowhere to record the dependencies that now matter, and the draft asks for the inventory’s design to be reviewed for exactly that reason. And the identification question — is this AI, and whose call is it — belongs to a designated control function acting as final arbiter, which cannot arbitrate what it never sees. What should have caught it is contractual: terms requiring notification when AI is introduced into an existing product, or the institution’s agreement before it is. Almost no contract signed before 2025 carries that clause, and this is the scenario it exists for.

§ 6 — Elsewhere

The same requirement elsewhere

Where another instrument addresses the same obligation. These are correspondences, not comparisons — the Council does not rank one framework against another.

  • EU AI Act

    Annex III point 5(b) brings creditworthiness assessment inside the high-risk perimeter by function. The draft Guidelines would reach a comparable population through the institution instead — different gateways, overlapping firms.

  • EU AI Act

    Article 26(5) and 26(6) deem certain financial institutions to satisfy monitoring and log-keeping through their existing internal-governance obligations. That page sets out the limits of the deeming precisely.

  • NIST AI RMF

    MANAGE 2 addresses mechanisms to supersede, disengage or deactivate a system that behaves outside expectations, which is the ground the draft covers as kill switches and override mechanisms.

A correspondence indicates that two instruments address the same underlying obligation. It is not a mapping endorsed by either body, not a statement that one satisfies the other, and not a judgement about which is more demanding.

§ 7 — When it applies

Consulted, closed, not issued

  1. 31 January 2026

    The date the consultation closed. It is not an application date and there is no application date: the Guidelines are not finalised, and the twelve-month transition after issuance discussed in the consultation paper is a proposal put to respondents, not a period running.

Certification

Assessed on the same standard of evidence

Every Council credential is examined on applied judgement against a published anchor, set out the way the obligations on this page are. The Certified Applied AI Associate, the Council’s flagship, is open to any adult today, its fee waived by a coupon code from the AI-Readiness Check, and the register lists what is open for enrolment.