Enterprise DNA
Key Findings

Before expanding AI agents, law firms should inventory access and rehearse how to shut it off across email, documents, and case systems.

Can Your Law Firm Stop a Misbehaving Agent?
Insight ai

Can Your Law Firm Stop a Misbehaving Agent?

Sam McKay

The question to answer before adding another agent

A law firm can give an agent access to email, shared documents, an intake mailbox, and a case system in a few minutes. The harder question is what happens when that agent does something it shouldn’t.

Can someone stop it now, not after an IT ticket sits in a queue? Can they revoke the right access without locking staff out of the matter? Can they tell what the agent read, changed, sent, or scheduled before it stopped?

The VB Pulse Agentic Security and Identity Report, published in September 2026, highlights a practical gap: few surveyed organizations could quickly stop a misbehaving agent. For a law firm, that’s not an abstract security problem. An agent working across client communications and case files can expose confidential information, send an inaccurate message, or make changes that staff only notice later.

The sensible next step isn’t to abandon automation. It’s to take stock of the agents already in use and rehearse how to shut them down before expanding their access.

Why law firms need a shutdown plan

Most firms don’t start with a formal agent program. A partner tests a tool on a contract. An operations lead connects an intake workflow to email. Someone asks an agent to sort incoming messages or create a matter summary. Each small step seems contained.

But agents can be connected to several systems at once. An intake agent might read new email, inspect a calendar, update a lead record, and send a response. A document-review workflow might read a folder of discovery files and write a memo into a matter workspace. If the firm doesn’t know which identity and permissions enable those actions, “turn it off” may mean disabling one screen while the agent retains access through another connection.

There are several reasons this can be difficult:

  • The agent’s connection may use a staff member’s account rather than a dedicated identity.
  • Access may be granted through a token or integration that isn’t visible in the system staff use every day.
  • More than one workflow may share the same credential.
  • The firm may not know which files or messages the agent accessed before the shutdown.
  • Staff may be unsure who has authority to stop a workflow outside business hours.

For a law firm, there’s a second consideration. Turning off access quickly matters, but so does preserving a reliable record of what happened. If an agent interacted with a client, matter file, or calendar, the firm needs enough information to assess the event and decide what follow-up is required.

A useful starting point is this guide to locking down agent access at a law firm. The immediate job is to make the access visible, assign a person who can act, and test that the shutdown works.

Inventory agents by task and access

Start with a plain inventory. It doesn’t need to be a new software project. A spreadsheet is enough if it names the workflow, owner, systems, permissions, and shutdown steps clearly.

Include formal deployments and informal experiments. Ask partners and staff what they’ve connected to firm accounts, what they use for drafting or review, and whether a workflow can read or write information without a person prompting each step. Include agents built by operations teams, vendor features enabled inside existing platforms, and tests that are still running.

For each agent, record:

  1. The business task. For example, classify web enquiries, prepare a first-pass contract summary, or draft a response for staff review.
  2. The accountable owner. Name a person who can approve changes and request a shutdown.
  3. The identity it uses. Is it a dedicated account, a staff member’s account, or a vendor integration?
  4. The connected systems. List email, document storage, calendar, matter-management software, and any other destination.
  5. The actions it can take. Separate read access from write, send, delete, or permission-changing access.
  6. The shutdown procedure. State exactly where to disable the workflow and revoke its credentials.
  7. The evidence it leaves. Identify where activity logs or a record of outputs can be reviewed.

Don’t assume that a workflow is safe because it only handles intake or internal summaries. An agent that reads confidential information still needs boundaries, even if a person approves its final message. This review of the permissions gap in law firms is useful when deciding which access is necessary and which is simply convenient.

Rehearse revoking access, not just pausing a workflow

A pause button is not the same as a shutdown. It may stop a scheduled run but leave an integration credential active. A user might also have an active session or another workflow connected to the same account.

Write a short runbook that covers the whole chain:

  • Stop new runs and scheduled tasks.
  • Disable or revoke the identity, token, or integration that grants access.
  • End active sessions where the connected system allows it.
  • Check for other workflows using the same credential.
  • Review recent activity and preserve the relevant logs and outputs.
  • Tell the workflow owner and the firm’s designated incident contact.
  • Decide whether affected clients, matter teams, or system administrators need to be notified.

Use a test environment or a low-risk workflow for the first rehearsal. Have someone who didn’t configure the agent follow the instructions. If the person needs the builder to explain where the access lives, the procedure isn’t ready.

Then test a realistic scenario. Suppose an intake workflow starts sending incomplete consultation confirmations. Can the responsible person stop the next send, revoke the email connection, and confirm no other process still has access? Suppose a review agent is writing summaries into the wrong matter folder. Can the firm halt new processing, remove write access, and identify what files it touched?

The aim isn’t to create a complicated incident plan for every small task. It’s to make the key steps obvious, repeatable, and proportionate to the information and actions available to the agent. For further context, see how governance frameworks apply to law-firm agents.

What this looks like in an intake workflow

Consider an Intake Voice Agent that answers calls after hours, during lunch, and on weekends. It captures the caller’s details, asks questions approved by the firm, performs an initial conflict check, and books a consultation into the firm calendar.

The operational benefit is straightforward. A call that might otherwise wait until the next morning gets a response and a clear next step. Intake delays can cost a firm a prospective matter, particularly when someone contacts several firms at once. After-hours enquiries can be harder to follow up on promptly, depending on the practice, staffing, and response time.

The workflow also creates access questions. Does the agent read the calendar or write appointments? Can it send an email confirmation? Where are call summaries stored? Does the conflict-check step expose existing client or matter data? Who can stop it if it begins booking consultations into the wrong calendar?

A responsible setup gives the agent only the access it needs. The firm sets the approved questions and boundaries, routes uncertain or sensitive enquiries to a person, and reviews the workflow’s records. The shutdown procedure names who can disable the voice workflow and revoke its connected accounts. Staff know how to handle calls while it’s offline.

The same discipline applies to the Matter Triage Agent. It can review incoming forms and emails, classify the practice area, score fit against rules set by the firm, and route a one-paragraph brief to the right partner. It should not decide that a potential client is accepted, send legal advice, or create a matter without the firm’s defined approval.

For document work, a Document Review Agent might perform a first pass on contracts, discovery batches, or matter files. It can flag clauses, summarise positions, and prepare an associate-grade memo for review. Before connecting it to a large collection of files, define which folders it can read, where its work product can be written, and who checks that the output belongs to the right matter.

These workflows address real manual work. Associates may spend substantial time on first-pass document review, which can make it a meaningful operational cost. Attorneys may spend time on document review, intake, and matter administration that never reaches a billable invoice. Automation may reduce some of that drag, but the workflow needs controls before it gets broader access.

Make the business case without ignoring risk

For a law firm, unbilled work can add up quickly. Time spent on repetitive review or administration can represent capacity that could have gone to client work, business development, or a more manageable workload.

Unbilled work can represent a significant opportunity to examine. Treat that as a range for identifying where to look, not a promised saving. The actual figure depends on attorney count, work mix, current intake conversion, document volume, and whether freed-up time can be redirected productively. Don’t count the same hour twice as both recovered billing and reduced staffing cost.

Shutdown controls protect the value of the automation. An agent that saves staff time but can’t be stopped promptly creates a different kind of business exposure. A well-defined stop procedure helps the firm keep useful workflows while limiting the time and access available if something goes wrong.

If you want to identify the right first workflow and map its controls, Book a 60-min Omni Audit. In 60 minutes, we’ll work with you to review agent tasks, shutdown and access controls, and priorities for future automation. There’s no deck.

You can also see Omni for law firms to understand how the audit fits a legal practice. The focus is on your actual systems, handoffs, and constraints, not a generic list of automation ideas.

Put the process into practice

A useful first review can happen in one working session with a partner, the person responsible for operations, and whoever manages the firm’s systems. List the agents and experiments they know about. For each one, identify the account, data sources, permitted actions, owner, and person who can shut it down. Then choose one low-risk workflow and test the instructions.

Pay particular attention to shared credentials. If several tools use the same staff account, revoking that account could interrupt legitimate work while failing to stop every connected agent. The firm may need a dedicated identity for each workflow, or at least a clear record of which integrations depend on each credential. A closer look at credential-sharing risk for law firms can help frame that review.

The same review should cover human responsibilities. Staff need to know when an agent is allowed to act, when a person must approve an output, and whom to contact if its behaviour looks wrong. Controls in software won’t help if nobody recognizes an unexpected message or knows who can pause the workflow. That’s the human side of agent security in legal practice.

For a ready-to-use worksheet, download the AI Client Intake Checklist for Law Firms. It gives your team a practical way to review intake steps and identify where a voice or triage agent needs boundaries, approvals, and a human handoff. You can also open the direct checklist file.

Expand only after the stop test passes

An agent’s value isn’t measured only by how much work it completes. The firm also needs to know what it can access, who is accountable for it, and how quickly its access can be removed.

Start with the workflows already in use. Rehearse stopping one. Fix any unclear permissions or missing logs. Then expand access in steps, with a named owner and a human review point for decisions that affect clients or matter records.

If you’re ready to map this for your firm, Book a 60-min Omni Audit. You’ll leave with the inventory, the shutdown steps, and a prioritized plan, without a deck. To review the offer first, see Omni for law firms.