# Agent Incident Playbook

General information, not legal advice. Adapt to your agents, contracts and jurisdiction. From Agent Authority, a legal reference by Obehi Ota.

## 1. Contain (First hour)

Owner: ______

- [ ] Stop the agent and any queued or scheduled actions.
- [ ] Where the Agent Transaction Addendum applies, send a suspension notice through the Channel and to the counterparty’s notice address. It takes effect for new Agent Actions [one hour] after receipt, and offers the agent made that are still unaccepted when the suspension takes effect lapse at that time (section 17).
- [ ] Revoke its tokens, keys and cards. Disable its client and stop token refresh, so it can’t obtain new tokens, and end any credentials its subagents hold. A revoked access token can keep working at a vendor until it expires, so ask key vendors to block the agent’s access directly until its tokens have expired. Don’t delete the agent, its configuration, or its logs.
- [ ] Tell the business owner and legal, and list each affected transaction’s deadlines, using the periods in the signed Addendum rather than the bracketed defaults. Under the Agent Transaction Addendum: to dispute the terms a Confirmation Message states, [one] business day after it is received (section 11(d)); to reject an action outside the Limits, [two] business days after the Confirmation Message is received or, if the company owed that message and failed to send it on time, after it was due, and not at all for custom or perishable goods once they have shipped (section 14); to avoid an error under the agreed procedure or give notice of an obvious error, [two] business days after the company receives the Confirmation Message or, if it owed the message and sent it late or never sent it, after the message was due (section 15(c)–(e)). Section 16 sets no deadline for avoiding a deal induced by planted instructions, but investigate and give notice promptly.

Why: If courts apply the rules for human agents by analogy, revoking authority ends the agent’s actual authority once the agent has notice of the revocation (Restatement (Third) of Agency § 3.10). How software receives notice is unsettled, so withdraw the agent’s credentials and change its instructions at the same time. Even after actual authority ends, apparent authority can continue until counterparties can no longer reasonably believe the agent is still authorized (§ 3.11), so tell counterparties and banks. If courts instead treat the agent as the company’s tool, the same steps still matter: they stop new actions through its credentials and put counterparties on notice.

## 2. Preserve (First 24 hours)

Owner: ______

- [ ] Issue a litigation hold if a dispute is reasonably likely.
- [ ] Export the mandate version, configuration, prompts, tool calls and their relevant results, identifiers of the credentials used (not the secrets), approvals, and outputs.
- [ ] Ask the provider in writing to preserve its logs, citing the contract.

Why: Federal Rule of Civil Procedure 37(e) applies when electronic information that should have been preserved for litigation is lost because a party failed to take reasonable steps and further discovery cannot restore or replace it. A court may remedy prejudice. An adverse inference, dismissal or default requires intent to deprive another party of the information’s use in litigation.

## 3. Establish authority (24–72 hours, alongside the steps below)

Owner: ______

- [ ] Do this alongside the phases that follow. Don’t delay a rejection or other notice that falls due before this work is finished.
- [ ] Identify which version of the mandate, and which credentials, were in effect when the agent took each action. Under the Agent Transaction Addendum, also identify the version of Schedule A then in effect.
- [ ] Trace each disputed action to the system that took it. For a handoff, compare the task requested with the order actually sent, using both parties’ records where available. Compare the action with the mandate and the permissions the receiving service actually checked. Distinguish a proposed order, an order sent or accepted, and a payment authorization.
- [ ] Record who approved each action, if anyone did, and what each counterparty had been told or could see about the agent’s limits, such as a signed Schedule A.

Why: This is the evidence for actual authority, apparent authority and attribution. See Guides 1 and 10.

## 4. Classify each transaction (By the first rejection or dispute deadline, and in any case within 72 hours)

Owner: ______

- [ ] **Check the signed limits first:** under the Addendum, crossing an internal limit such as the company-wide monthly cap is not itself grounds for rejection. An approval reference satisfies the approval requirement between the parties, but does not lift the amount cap or other Limits. Compare the order with Schedule A before choosing a remedy.
- [ ] **Within the mandate:** identify who acted and whether the parties completed the steps required for a binding deal. Check any defense or cancellation right before deciding whether to perform. Look for an obvious error, instructions the counterparty planted that induced the deal, or an error the counterparty would have caught by running its agreed checks. Under the Addendum, each of these can be unwound or avoided (sections 15 and 16); avoiding for a missed check requires that the company ran its own checks. Signs of manipulation alone don’t establish the section 16 right, so investigate before relying on it.
- [ ] **Outside the mandate, counterparty had no notice:** treat the transaction as possibly binding. Check the contract terms and any defenses, then negotiate.
- [ ] **Outside the mandate, counterparty had notice:** the company may not be bound, but notice alone doesn’t settle it. Dispute the transaction promptly in writing and reserve rights. Check for any rejection, avoidance or cancellation right (for example, Addendum section 14) and exercise it before its deadline. Don’t use what was delivered; keep any goods safe and arrange their return as the contract or law requires.
- [ ] **Obvious error:** notify the counterparty at once and ask it to unwind the transaction. Under the Addendum, give notice within [two] business days after receiving the Confirmation Message. If your company owed the message and missed the deadline to send it, count from when it was due (section 15(d)–(e)).
- [ ] **Evidence for each remedy:** for a rejection, the Confirmation Message and when it was received or due, and the version of Schedule A showing the action was outside the Limits (section 14); for avoiding an error under the agreed procedure, a record that the company ran its own checks and that the counterparty’s check would have caught the error (section 15(c)); for an obvious error, what the party receiving the erroneous action saw and why a reasonable recipient in its position would have recognized the error then (section 15(d)); for planted instructions, the content, where the counterparty placed it and how it led to the action (section 16).
- [ ] **Possible manipulation or compromise:** treat it as a security incident as well as a contract issue. If content the counterparty planted induced a transaction, consider avoiding it under Addendum section 16 and give notice promptly. Section 16 doesn’t cover stolen credentials or content planted by someone else; for those, look to the rejection right for actions outside the Limits (section 14), the error rules (section 15) and the Agreement.

Why: Mistake, notice and security procedure rules differ by category. See Guide 5. Wrongful rejection can give a seller remedies (UCC § 2-703), and even a rightful rejection of goods may require holding them with reasonable care for the seller to collect (UCC § 2-602(2)(b)).

## 5. Notify (As soon as possible, and before each recipient’s notice deadline)

Owner: ______

- [ ] **Bank (wire or other funds transfer):** report a disputed payment order immediately. If UCC Article 4A governs, check the account agreement and two separate notice rules. Section 4A-204 addresses interest on a refund for an unauthorized order. Section 4A-505 sets a deadline for objecting to the debit.
- [ ] **Corporate card issuer:** report a disputed charge promptly through the issuer’s dispute process. Check the card agreement and applicable network deadlines. For an unauthorized business credit card charge, check Regulation Z § 1026.12(b), including any agreement permitted by § 1026.12(b)(5). The consumer billing-error procedure in § 1026.13 generally does not apply to business-purpose cards.
- [ ] **Counterparties:** dispute unauthorized deals promptly and in writing, reserve rights, and exercise any rejection or cancellation right before its deadline.
- [ ] **Agent provider:** give the notice your contract requires.
- [ ] **Insurers:** check notice conditions in cyber, crime and E&O policies.
- [ ] **Individuals and regulators:** if personal data was exposed, check breach notification laws.
- [ ] **Board or audit committee:** report if the incident is material.

Why: Late notice can cut off rights against banks, providers and insurers.

## 6. Avoid ratification (Throughout)

Owner: ______

- [ ] Don’t use goods or services the agent obtained outside its mandate.
- [ ] Pay disputed invoices only under a written reservation of rights, if at all.
- [ ] Route counterparty communications through one person; don’t let the agent reply.

Why: Keeping a benefit can affirm an unauthorized deal if the company knows the material facts or chooses to affirm despite gaps in its knowledge (Restatement (Third) of Agency §§ 4.01, 4.06). A buyer can separately accept goods by failing to reject them effectively after a reasonable opportunity to inspect (UCC § 2-606(1)(b)).

## 7. Recover and fix (Within 30 days)

Owner: ______

- [ ] Complete any cancellations and returns with counterparties, and pursue any claim against the agent’s provider under the provider agreement.
- [ ] Find the root cause: whether the mandate allowed too much, a credential gave more access than the mandate, a control failed, or the agent was manipulated.
- [ ] Update the mandate, the controls and the counterparty terms as the root cause requires. If Schedule A under the Agent Transaction Addendum needs to change, follow section 17: a narrowing takes effect [one] business day after the counterparty receives notice, and a widening only when an Authorized Individual of the counterparty accepts it in writing. Record each change and the reason for it.

Why: A documented fix is evidence of reasonable care if the same thing happens again.

## Don’t

- Delete the agent, its logs or its configuration
- Let the agent respond to counterparties about the incident
- Use what the agent obtained before deciding whether to reject it
- Make public statements before the facts are established
