AI Agents Discovered Accessing Bank Accounts Without Approval

For the past few months, the news has been handing us stories about AI agents running amok around the internet. Sometimes alone, other times in small packs or swarms. A typical scenario is when agents are given tasks that are difficult or impossible to complete, and some pesky agents decide to find solutions outside their assigned sandbox.

But it’s not only an issue with the frontier AI model developers. Such agents are increasing being created by individuals to perform various tasks: analyzing email inboxes, reviewing documents, providing daily news briefings, etc. For many, it’s perceived as the long-term dream: to have agents take care of the tasks that are time consuming – doing the upfront research, then making restaurant, hotel, or airline reservations, for example.

But how far should you go? What information do you feel comfortable sharing with an AI agent? There are two main areas that concern me the most. The first is healthcare. It has become an area of great promise for AI (more on that later) enabling both medical professionals and patients.

The second area of concern involves finance. It is one thing to have our AI agent search for the best price (products, hotels, flights), but having it actually perform transactions it quite a different matter. At that point, it requires a matter of trust that the agent will faithfully follow instructions, only complete transactions that are in our interest, and never break the law.

But as we have recently witnessed AI agents exhibit blatantly rogue behavior, is handing over your credit card information wise? And how about letting an agent rummage through your online bank account? And what do the banks & financial institutions think about this new AI agent capability?

So it should come as no surprise that this video caught my attention. The fact that such agents can potential perform actions, in addition to making inquiries, raises questions regarding security. I think of the issue as three scenarios.

A new report is highlighting how hard it could become to keep your money safe. Axios says major US banks are detecting what they believe is unauthorized actions by third-party AI agents operating inside customer accounts.

Three AI Agent Banking Scenarios

Unintended Action

The user initiates a task, and the agent attempts to carry it out, but in doing so, takes liberties with how it executes the instructions. It may make assumptions, choose an unexpected method, or take an action the user did not anticipate. In this case, we’ll assume no harm was done, so it serves as a learning experience for the user.

Out-of-Scope Action

The user authorizes a task, but the agent performs an additional action that was not included in the instructions. The action may be an attempt to accomplish the user’s broader goal, a mistaken assumption about what is permitted, or a failure to respect a restriction. Or this may involve an unapproved movement of funds between accounts, or a payment that was made without explicit instructions to do so.

Malicious Action

An AI agent is engaged or manipulated by a bad actor (cyber criminal) in order to gain unauthorized account access, and in doing so steals information or initiates fraudulent transactions. If an action removed money from a user’s account, they would likely suffer financially, as it may be a transaction that can’t be reversed.

Banking & Finance Viewpoint

Banks already have rules in place that govern third-party access, payments, and account security, but they’re having to evaluate how these rules apply when AI agents are acting on a customer’s behalf, with their permission. Retail websites and credit card issuers are also having to evaluate whether they will allow such agents to perform transactions. Expect to see a lot of updates to the terms of service issued by financial institutions in the coming year.

Government Viewpoint

Governments also have several legal statutes and policy tools in place that address financial transactions, and cybersecurity, but it’s unclear as to how those laws apply to malicious AI-agent activity.

In the United States, Senators Josh Hawley and Chris Murphy have introduced the AI Agent Accountability Act, which would address civil and criminal liability for agent operators and developers in certain hacking incidents. We’ll have to wait and see what the final version says, and whether it is signed into law.

Meanwhile, the House of Representatives is working on the Stop Rogue AI Act , which will direct the National Institute of Standards and Technology (NIST) to develop standards for identifying, verifying, tracking, and controlling AI agents. The bill also proposes actions such as monitoring, reliable agent identity, action logs, and the ability to revoke access.

But there’s a legal quandary at play when it comes to the actions of AI agents. How do you determine criminal intent, and to whom is that intent applied; the user of the agent, or the developer? Who is at fault if an agent behaves badly? What is an agent colludes with another agent, who then decides to commit a crime? Is this an aiding and abetting scenario? At the present moment, there doesn’t seem to be clarity with regards to accountability.


To expand on this topic, and take a broader view of how people are using AI agents, I asked Reflection.AI to create a set of tables that would highlight the most common use cases.

As you can see, the issues of governance, alignment, policy, and safety are no longer confined to those building frontier AI models or government officials. There will potentially be hundreds of companies creating agents that touch sensitive personal data.

Common AI Agent Use Cases for Everyday Tasks

Below are the most common ways people are using AI agents today, plus how they’re building them for everyday life. Grouped by task area with typical tools.

1. Personal Productivity & Administration

Use case What the agent does Common tools
Inbox triage Reads email, labels, drafts replies, schedules follow-ups Zapier/Make + Gmail API, Superhuman AI, Copilot
Meeting prep & notes Joins calls, transcribes, summarizes action items, updates CRM Otter, Fireflies, Notion AI, Granola
Calendar orchestration Finds mutual free time, books rooms, sends invites Cal.com AI, Reclaim, Motion
Task routing Turns Slack messages/emails into tickets with priority Linear, Jira automation, n8n
Document drafting First drafts of memos, SOPs, proposals from bullets ChatGPT, Claude, Gemini, Notion

Most people use no-code automations (Zapier, Make, n8n) that chain an LLM call between triggers and actions. Power users build custom GPTs / Claude Projects with file uploads and instructions.

2. Research, Learning & Decision-Making

Use case What the agent does Common tools
Deep research Multi-step web search, synthesis, citations Perplexity, ChatGPT Deep Research, Gemini Deep Research
Study buddy Quizzes, flashcards, explains concepts at your level Khanmigo, Anki + AI plugins, custom GPTs
Comparison shopping Scrapes specs, prices, reviews, outputs table Browser-use agents, Perplexity, custom scrapers
Travel planning Builds itinerary with constraints (budget, kids, weather) Mindtrip, Layla, ChatGPT + Maps
Financial literacy Explains terms, simulates budgets, flags anomalies Copilot in Excel, Monarch, custom agents

“Research agents” often use tool-calling loops (search → read → summarize → verify) rather than single prompts.

3. Software & Data Work

Use case What the agent does Common tools
Coding copilot Autocompletes, refactors, writes tests, fixes bugs GitHub Copilot, Cursor, Windsurf, Claude Code
Data cleaning Parses messy CSVs, dedupes, normalizes formats Pandas AI, Julius, ChatGPT Code Interpreter
SQL/analytics Natural-language → query → chart Hex, Mode, Databricks Genie
DevOps triage Reads logs, suggests root cause, drafts PR Datadog Bits AI, PagerDuty, custom agents

Developers use IDE agents (Cursor/Windsurf) or CLI agents (Claude Code, Aider) that can edit files and run commands with human approval.

4. Content & Media

Use case What the agent does Common tools
Social media management Drafts posts, schedules, repurposes long → short Buffer AI, Hootsuite, Typefully
SEO/content ops Keyword research → outline → draft → meta tags Surfer, Jasper, Frase
Video/audio editing Removes filler, captions, clips highlights Descript, Opus Clip, CapCut AI
Image generation Marketing visuals, thumbnails, product shots Midjourney, DALL·E, Firefly

“Content pipelines” are often multi-agent workflows (researcher → writer → editor → formatter) built in n8n or LangGraph.

5. Home, Health & Daily Life

Use case What the agent does Common tools
Smart home routines “When I leave, lock doors, adjust thermostat, start robot vacuum” Home Assistant + LLM, Alexa Routines
Meal planning Generates grocery list from dietary constraints & pantry ChatGPT, Whisk, Samsung Food
Fitness coaching Adjusts workouts based on recovery/sleep data Whoop Coach, Garmin, custom GPTs
Mental health journaling Reflective prompts, mood tracking, CBT exercises Woebot, Wysa, custom agents

Usually single-purpose custom GPTs or Home Assistant blueprints with local LLMs for privacy.

6. Customer-Facing & Small Business

Use case What the agent does Common tools
Website chat Answers FAQs, qualifies leads, books demos Intercom Fin, Drift, Zendesk AI
Review management Drafts responses to Google/Yelp reviews Birdeye, Podium, custom GPTs
Inventory reordering Monitors stock, drafts POs, emails suppliers Shopify Flow, Zapier
Invoice chasing Sends reminders, escalates, logs in accounting QuickBooks AI, Xero, custom agents

How People Actually Build Them (Spectrum)

Level Approach Example stack
No-code Drag-and-drop automations Zapier/Make + ChatGPT action
Low-code Visual agent builders n8n, Langflow, Flowise, Voiceflow
Pro-code Frameworks with memory/tools LangChain, LlamaIndex, CrewAI, AutoGen
App-native Built-in agents in SaaS Notion AI, Copilot, Salesforce Einstein

 

How Can the UN Provide AI Governance Going Forward?

The previous article titled The United Nations’ Evolving Role in Global AI Governance ended with this proposition:

The UN can play an important role by helping countries agree on a common framework for testing frontier models, as well as reporting, investigating and learning from significant AI incidents. Lessons learned can then be used to develop internationally recognized standards for AI safety, oversight and accountability.

It didn’t take long before a colleague reached out and asked, “What, specifically, do you think the UN can do to put this proposal into practice?“

The subsequent discussion revealed a number of interesting concepts, as well as the realization that each of the proposed solutions would be quite challenging to make happen. But that shouldn’t prevent them from being brought to light.

From Incidents to Global AI Oversight

Image: Mark Lovett / AI GAPS — Generated with ChatGPT Images 2.5

1. Establish a global AI incident reporting framework

Nations, as well as frontier AI model developers, can’t learn from incidents they don’t know about or discover months after the fact. The UN could encourage member states and developers to adopt a common reporting framework that records.

  • What exactly happened and when it was discovered
  • Which AI system and agent capabilities were involved
  • What the system was instructed to do versus what it actually did
  • Whether information systems, people, data or infrastructure were affected
  • Which safeguards failed, what harm occurred, and what remediation followed

This would build on work already underway at the OECD, whose common reporting framework proposes 29 criteria for describing AI incidents consistently across countries and sectors.

Why it matters: Without consistent reporting, the international community only sees headlines for major incidents rather than discerning developing patterns that could inform policy decisions.

2. Create an international AI incident repository

The reporting process should feed into a shared, searchable source of information. The UN could coordinate a repository, or work with the OECD’s existing AI Incidents and Hazards Monitor, to make verified information available to researchers, testing authorities, governments and the public. Such a repository could distinguish:

  • Confirmed incidents from alleged or unverified reports
  • Human-directed misuse from unintended AI agent behavior
  • Actual harm incurred from near misses and potential hazards
  • Unauthorized access from successful compromise and confirmed damage
  • Independent incidents from multiple reports related to one particular event

Sensitive information could be shared through protected channels with qualified investigators and government officials, while public summaries would still provide appropriate transparency.

Why it matters: A common evidence database could reveal recurring weaknesses across systems, such as inadequate sandbox safeguards, excessive permissions being granted, poor monitoring of agent activity or delayed disclosure of critical incidents. The OECD already operates an incident monitor, so the UN could coordinate with and build on existing work rather than create a competing database.

3. Use independent scientific research to identify systemic risks

Incident reports document what happened in the past. Independent research helps explain why and how it happened, whether the same failure could recur, and what other potential risks might be emerging.

The UN’s Independent International Scientific Panel on AI is well positioned to contribute their expertise. Its mandate includes evidence-based assessments of AI capabilities, opportunities, risks and impacts. Its preliminary report identifies important domains including security, reliability, human rights, democracy and child safety.

The UN could ask the Panel to assess recurring incident patterns and report on questions such as:

  • How often do agents exceed their intended permissions?
  • Which containment and monitoring measures fail most frequently?
  • What agentic capabilities make certain types of incidents more likely?
  • Which safeguards have evidence of effectiveness, and how often are they used?
  • What risks remain difficult to test before deployment or monitor after deployment?

Why it matters: AI governance policies should respond to demonstrated failure mechanisms regardless of scope, not just to the most alarming individual incidents.

4. Develop internationally recognized minimum safety standards

Once recurring failure modes are understood, the UN could help countries agree on minimum expectations for AI systems, especially those using agents that take actions in external environments.

Possible standards include:

  • Least-privilege access: Agents receive only the permissions required for their task.
  • Isolation and containment: Testing systems cannot freely reach production infrastructure or the public internet unless explicitly authorized.
  • Human authorization: Sensitive actions, such as transferring funds, changing critical systems or submitting official reports, require appropriate approval by a human.
  • Continuous monitoring: Developers maintain records of agent actions and implement systems able to detect attempts by any agent to bypass safeguards or violate protocols.
  • Independent evaluation: Systems undergo proportionate testing before deployment and after significant changes.

UNESCO’s Recommendation on the Ethics of Artificial Intelligence already calls for measurable safety and transparency standards, auditability, traceability, monitoring and redress.

Why it matters: A common baseline would let countries implement and enforce protections through their own laws while making expectations more consistent internationally. In this way, the public could see when companies or governments were not meeting minimum safety standards.

5. Clarify responsibilities and disclosure obligations

The incidents raise a basic governance question: when an AI agent takes an unauthorized action, who must report it, investigate it, contain it and help remedy the consequences?

An international framework could distinguish responsibilities among:

  • Developers who design and train the model
  • Deployers who integrate it into operational systems
  • Users who provide it with instructions or grant permissions
  • Operators and infrastructure providers who control access and containment
  • Regulators and affected authorities who investigate and enforce applicable laws

It could also establish recommended timelines for reporting serious incidents, preserving evidence, notifying affected parties and documenting corrective action.

Why it matters: Accountability becomes extremely difficult when organizations use different definitions of an incident, operate under different disclosure timelines, and adopt different assumptions about who is responsible.

6. Turn lessons learned into an ongoing international process

A one-time declaration will not keep pace with a rapidly evolving technology. The UN could use its Global Dialogue on AI Governance as a recurring forum where countries examine incidents, compare national responses and update shared recommendations.

Each annual cycle could follow a simple process:

  • Collect incident reports and technical evidence
  • Have independent experts identify recurring failure patterns
  • Ask governments and stakeholders to evaluate possible responses
  • Publish recommendations, model reporting rules and proposed safety standards
  • Review implementation and assess whether incidents and harms are decreasing

The Global Dialogue is already designed to facilitate international cooperation and exchange best practices, but it is not a negotiating forum and does not itself produce binding agreements.

Why it matters: The UN could help create a continuous feedback loop between real-world experience, scientific analysis and international policy.

Wrap up: From incidents to international action

The long list of incidents involving AI agents are not simply stories about this technology behaving unexpectedly. These incidents should be treated as case studies that exemplify the challenges of governing increasingly capable systems that can act with agency, and do so across digital boundaries.

They raise questions about training, testing, containment, permissions, monitoring, disclosure, responsibility and accountability. And because AI systems don’t recognize national borders, those questions cannot always be resolved by one country acting alone. Without international cooperation, such incidents will never be fully dealt with.

The United Nations does not need to become a global AI regulator in order to make an important contribution to the framework. It is well-equipped to help countries agree on how such incidents should be reported, establish a shared evidence base, commission independent analysis to uncover threats and patterns, develop common safety standards, and clarify expectations for disclosure and accountability.

And the processes need to be iterative: document actions, learn from incidents, identify patterns, develop policies, implement safeguards, and discern whether those safeguards work. Everything learned becomes part of the processes that creates the next frontier model.

Even with the best of intentions, such practices won’t eliminate AI risk. Nor will it guarantee that every country or company complies with the guidance or meets expectations. But if implemented properly, it could replace the current system of fragmented responses with a more coordinated approach to AI governance and policy implementation.

The goal should not be to create a global institution that predicts and prevents every AI failure. It should be to build an international system that detects failures, learns from them, shares that knowledge with transparency,  and makes future failures less likely.