Table of contents
The short answer

Give agents the smallest useful set of tools and permissions. Require an independent authorization check for the exact consequential action. Then test that changed, replayed or revoked authority cannot get through.

3distinct permission questions
6control areas to review
5tests before production

Counts describe the framework in this guide, not incident statistics.

1. What was actually reported?

Axios reported concerns about agents accessing bank accounts. [6] Axios later reported banks said they had seen no evidence of hacks affecting customer funds or accounts. [7]

The bank’s own statement provides primary-source context. In its October 13 earnings discussion, JPMorgan Chase described blocking credential-sharing and screen-scraping agent access where possible while developing safer approaches. That is a concern about how agents access accounts; it does not establish that an attacker compromised the bank. [1, pp. 3, 10]

This is an authorization and governance problem

This article does not describe a disclosed CVE or a product-specific defect with a fixed software version. Predictions about wider financial disruption are opinions. The practical question is whether a system can stop an agent from doing something its user never authorized.

2. Three different permissions

“The customer connected the account” is only the beginning. Access to an account, permission to use a particular access method, and authority to perform a particular action answer different questions.

Three separate checks: customer account access, provider-permitted access method, and customer authority for the exact action.
Passing one check does not automatically satisfy the others.
Three decisions to keep separate
DecisionQuestion to answerWhat it does not establish
Account accessDid the customer allow this agent to access this account and these data?Permission to make every change available through that account.
Access methodDoes the provider permit this integration or method of access?A customer mandate for a payment or other consequential action.
Exact actionDid the customer authorize this recipient, amount and operation within the allowed time?Permission for a different recipient, amount or later reuse.

This is a practical review framework, not a universal statement of bank terms. Review the actual bank or provider agreement and integration rules. A customer’s permission does not automatically make every access method acceptable.

Hypothetical example: finding a bill versus paying it

A customer asks an assistant to find the electricity bill and summarize it. The assistant can also initiate payments through its connected tool. Finding the bill does not authorize paying it. Even “pay this bill” needs a defined recipient, amount and account, with the approved details checked at execution. This is an illustration, not a reported banking incident.

3. How excessive agency creates risk

OWASP describes excessive agency in terms of too much functionality, too many permissions, or too much autonomy. An agent does not need malicious intent to cause harm: it can misunderstand a task or use a capability outside the intended scope. [2]

A tool that can both retrieve an invoice and change its payment destination combines very different powers. A general-purpose browser or shell may expose more operations than the task needs. A broad credential can turn an incorrect decision into a real change.

Untrusted retrieved content can also attempt to redirect an agent. Test that boundary, but do not confuse a possible failure mode with an observed cause: the banking discussion cited here does not establish that prompt injection caused the reported access. OWASP’s agent guidance treats input handling, tool controls and authorization as parts of a broader defense. [3]

Read-only is narrower, not risk-free

A read-only tool removes some write risks. It can still expose balances, customer records or sensitive documents. Limit which data it can read, where those data can go, and what appears in logs.

4. Put authority into the system

Start with an inventory: each agent’s owner, identity, tools, accessible resources and write powers. Remove capabilities it does not need. Prefer narrow operations, such as retrieving an approved invoice, over unrestricted account access. OWASP recommends least privilege and controls around tool use and consequential actions. [3]

Separate the proposal from execution. The model can propose an action. An independent control should decide whether that exact action may run. A prompt saying “ask permission first” is not an authorization mechanism.

Model proposes an action; approval binds its exact details; an independent authorization gate checks them before execution. Changed, expired or revoked authority is denied.
A recommended design pattern. Authorization is checked outside the model, immediately before execution.
Controls and the evidence to keep
ControlImplementation questionUseful evidence
Narrow identity and toolsCan this identity perform only the task’s necessary operations on allowed resources?Owner, tool list, permission policy and denied out-of-scope request.
Bind the approvalDoes approval cover the precise recipient or resource, amount or parameters, tool and expiry?A recorded mandate and a rejection when approved details change.
Check at executionAre current permissions and the mandate checked independently before the action runs?Revoked or expired authority fails closed.
Prevent reuseCan an approval be replayed or a retry duplicate a consequential action?Replay protection and idempotency tests appropriate to the operation.
Make delegation revocableCan an owner stop the agent and remove delegated authority?Attributable delegation records and a tested revocation path.
Record outcomes safelyAre executed and denied actions logged without exposing secrets or unnecessary customer data?Redacted records tying actor, mandate, decision and outcome together.

The table translates OWASP’s guidance into implementation and review questions; it is not a claim that these were the mechanisms behind the banking report. [3]

Disconnect the authorization, not just the app

CFPB’s July 2020 financial-data-sharing guidance explains that uninstalling an app does not end data sharing, and a password change may not terminate every connection. Explicitly revoke the service’s access and, where applicable, separately request deletion of retained data. This is historical consumer guidance, not a new AI advisory. [8]

In AWS, scope IAM actions and resources, constrain role assumptions, and use permissions boundaries where appropriate. Keep development and security administration separate. These controls limit what an agent identity can do; IAM alone does not establish that a customer approved a particular transaction. [4]

NIST’s February 2026 concept paper discusses agent identity, authorization, delegation and logging. It is a draft concept paper, not a binding standard, and its proposed scope excludes external untrusted agents. Use it as design context, not as proof that a third-party banking agent is approved. [5]

5. Five tests before production

Run these recommended tests in a controlled environment with synthetic data and non-production actions. They test your controls; they are not claims about demonstrated banking attacks. Record both the expected decision and what actually executed.

  1. Out-of-scope action: give a read task to an agent with a write-capable integration. The system must reject the unauthorized write.
  2. Changed target after approval: approve one recipient or resource, then change it or the amount. The earlier approval must not authorize the changed action.
  3. Replayed approval: submit the same authorization again. It must not create an unintended second action; safe retries need operation-specific idempotency.
  4. Revoked permissions: remove delegated access before execution. The action must fail closed even if the agent planned it earlier.
  5. Malicious retrieved content: include instructions in a document that request an unrelated action. Those instructions must not create authority or bypass the execution gate.

Also check expiry, authorization-service failures and log redaction. A successful demonstration is evidence for the tested configuration, not a guarantee against every future failure. [3]

6. A practical first-week plan

Start with exposure. List agents already connected to production systems. Assign an owner, identify sensitive reads and consequential writes, and pause unnecessary powers while reviewing them.

Define the mandate. Choose one high-impact workflow. Write down exactly what the agent may propose, what needs approval, how approval is bound to the action, and which system enforces it.

Prove the boundary. Run the five tests, fix gaps, and preserve the results. Confirm that revocation works and that operators can see denied as well as completed actions.

Plan for failure. Decide who can stop execution, who investigates, and which recovery options actually exist. Do not assume a payment or other external action can be undone. MFA, compliance reports and model instructions do not replace these action-level checks.

The question to ask before granting production access

Can this agent do something the user never authorized—and will our systems stop it before execution?

7. References

Primary guidance and news reporting. In-text numbers link to the sources below.

  1. JPMorgan Chase: Q3 2026 earnings transcript, 13 October, pp. 3 and 10
  2. OWASP: Excessive Agency
  3. OWASP: AI Agent Security Cheat Sheet
  4. AWS Generative AI Lens: scope permissions for AI agents
  5. NIST NCCoE: agent identity and authorization concept paper, February 2026 draft
  6. Axios (22 Oct)
  7. Axios (23 Oct)
  8. CFPB: financial data sharing guidance, 24 July 2020 (archive)

Test authority before granting access.

Truva can help review agent permissions, approval paths and execution controls, then turn findings into a practical remediation plan.

Discuss your AI security review