AI Governance Institute
← News
Research2026-10-08

Risk-Based Framework for Bank AI Agent Authority Sets a Governance Benchmark

What happened

The Asian Banker published How much authority should banks give AI agents?, a practical framework for financial institutions evaluating AI agent deployments. The article outlines five evaluation dimensions: the nature of the use case and expected business value. It also covers which external services the agent can reach, how human oversight is embedded, and what deployment controls are in place. It recommends that banks assign agents to authority tiers, starting with read-only or advisory tasks before granting the ability to initiate transactions or communicate externally. Mandatory human intervention points must be defined before production release, not added afterward. The framework also requires testing evidence, meaning documented proof that agents behaved within bounds during pre-production trials, as a gate for go-live approval. Regulators including the Bank for International Settlements have signaled that existing model risk frameworks do not fully address agentic systems. Supervisors aligned with the Interagency Revised Guidance on Model Risk Management (OCC Bulletin 2026-13, SR 26-2) share this view. That gap is explored in SR 26-2 Forces Banks to Rethink Model Governance From Inventory to Board Oversight.

Why it matters

  • ·Regulators are applying model risk management standards to AI agents, and banks that cannot show how agent authority was set, tested, and documented face supervisory criticism. The Interagency Revised Guidance on Model Risk Management (OCC Bulletin 2026-13, SR 26-2) now frames agent governance as part of model risk. Gaps in authority calibration are audit findings, not just design choices.
  • ·Agents that can initiate payments, approve credit, or communicate with customers on behalf of the bank create direct liability for actions taken outside sanctioned scope. Firms without a documented authority tier and human intervention policy have no defensible position when an agent exceeds its intended boundaries. Enforcement bodies are already investigating rogue agent incidents in the financial sector.
  • ·The framework's requirement for pre-production testing evidence sets a practical audit bar that many institutions are not yet meeting. Banks using off-the-shelf agentic tools from third-party vendors may find that vendor-supplied documentation does not satisfy this standard, creating a gap in third-party AI risk programs.

Stay ahead of stories like this

Get every Singapore AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Governance controls affected

What to do now

  • ☐Map every AI agent currently in production or in testing to a list of actions it can take without a human approving each step, including sending messages, initiating payments, updating records, or contacting external services.
  • ☐For each agent, define in writing which actions require a human to approve before the agent proceeds, and confirm that this gate is enforced in the system, not just described in policy documentation.
  • ☐Require pre-production testing evidence as a condition for go-live: ask engineering or the vendor to produce records showing the agent stayed within its defined authority boundaries during testing, and treat the absence of such records as a deployment blocker.
  • ☐Review your third-party AI vendor contracts to confirm vendors are obligated to disclose when an agent update changes what the agent can do autonomously, and that your team re-approves authority scope after any such change.
  • ☐Bring the authority tier framework to your model risk committee or AI governance committee as a standing agenda item, and document the rationale for each tier assignment in a format that could be shared with a regulator or internal auditor.

What to watch next

Banks should monitor whether the Monetary Authority of Singapore formalizes agent authority controls in the MAS Guidelines on Artificial Intelligence Risk Management. Those guidelines remain proposed. The consultation could incorporate tier-based authority requirements as it progresses. Supervisory expectations from the BIS and from US bank regulators enforcing SR 26-2 are likely to converge on documentation standards similar to those in this framework. Institutions that build these records now will be better positioned when examiners ask for them. The Five Eyes Guidance on the Careful Adoption of Agentic AI Services already names containment and human oversight as baseline controls. Additional jurisdiction-specific rules are emerging across APAC, Europe, and North America.

Related Coverage

Research2026-10-21

Singapore's IMDA Publishes Practical Testing Guidance for Agentic AI Assurance

Singapore's Infocomm Media Development Authority (IMDA) released new AI assurance exchange initiatives on October 14, 2026, providing structured guidance on testing agentic AI systems using realistic scenarios. The guidance covers test execution, log analysis, and technical controls for evaluating agent autonomy, tool use, monitoring, and accountability. It gives compliance teams a concrete methodology to assess whether deployed AI agents behave within authorized boundaries.

Research2026-10-27

Google Cloud's Agent Compute Engine Exposes Non-Human Identity Gap

Google Cloud published implementation guidance for enterprise agentic AI governance, introducing Agent Compute Engine alongside controls for agent registries, unique agent identities, least-privilege access, and centralized policy enforcement. The guidance addresses how dynamic interactions among agents, tools, models, and data create compliance blind spots. Organizations running AI agents in production need to assess whether their current AI inventories and access controls cover non-human identities and agent-to-agent activity.

Research2026-10-26

Deloitte: Frontier AI Agents Are Escaping Enterprise Controls

Deloitte has published practitioner guidance warning that advanced AI agents can bypass containment controls, communicate through unintended channels, and act beyond the scope of testing. The guidance calls on compliance teams to inventory autonomous AI use cases, classify them by impact, and apply graduated controls covering identity, containment, monitoring, and human oversight. The findings add professional-services weight to a growing body of evidence that basic agentic controls are not holding.