When Legal AI starts taking action, governance has to catch up


When Legal AI starts taking action, governance has to catch up


For the last few years, most Legal AI use cases have followed a familiar pattern:

Ask a question → get an answer → review the output.

But the market has already moved beyond that model.

Three months ago, Anthropic introduced Claude Tag, allowing teams to bring Claude directly into Slack, give it access to selected tools and context, and delegate work to it much like they would to another team member.

Last week, the same shift became even more visible in Legal AI: Legora launched Intake, and Harvey introduced its own intake workflow for in-house legal teams.

The interesting part is not another AI feature. It is what this signals for legal teams:

“
AI is no longer just answering legal questions. It is becoming part of how legal work gets done.

And once AI starts taking action, another question becomes much more important.

Who decides what the agent is allowed to do?

If an AI agent is part of a legal workflow, the team needs to decide:

  • What information can it access?
  • Which contracts, policies or business data can it read?
  • What actions can it take autonomously?
  • Which tasks require human approval?
  • Can it communicate with the business on Legal’s behalf?
  • Who remains accountable for the final output?

Legora’s own approach reflects this shift: how far the Agent goes is determined by the legal team, request type by request type, with lawyer review as the default.

This is where AI governance becomes part of workflow design.


Context tells the agent how to work.
Governance defines the boundaries.

For an AI agent to perform legal work effectively, it needs context:

  • Role — what it is responsible for.
  • Knowledge — the business and legal information it needs.
  • Memory — relevant previous decisions and work.
  • Skills — the process it should follow.

But access to context should not mean access to everything. As legal teams give AI agents more capabilities, they also need to define roles, permissions, approval points and accountability around those agents.

This is exactly what we will explore in our next workshop:

We’ll walk through how to configure data access, manage permissions, and establish boundaries for AI agents working with sensitive business information.

The goal is not simply to give AI more autonomy.

It is to make that autonomy controlled, appropriate and accountable.

One question to ask your legal team


If an AI agent joined one of your legal workflows tomorrow:

What would you allow it to access?​
​What would you allow it to do?​
​And where would you require a lawyer to step in?

As Legal AI moves from assistance to action, those questions become just as important as choosing the model itself.

Join us at our upcoming workshop to explore these questions in practice and see how roles, access levels and approval boundaries can be configured in Claude.

Legal Nodes Newsletter

Get emails from the Legal Nodes team.

Read more from Legal Nodes Newsletter

AI can monitor the regulation. Context tells it whether it matters to you. The Legal AI race is no longer just about who has the smartest model. For legal teams, the more important question is becoming: “ Does the AI understand enough about your business to actually do the work? A regulatory update is a good example. A model may be able to summarise what changed. But before Legal can advise Product, Operations or HR, someone still needs to determine: which entity or product is affected;...

What can your regulatory feed not tell you about your business? When legal teams discuss regulatory monitoring, the conversation often starts with sources: which websites to check, which alerts to subscribe to, and how frequently to look for changes. Those are sensible questions, but they only cover the first part of the work.Once an update appears, someone still has to work out whether it applies to the company, what it could mean for a particular team or process, and whether it calls for...

"The Fintech Brief" by Iryna Kuzyk & the Legal Nodes team A quick note from Iryna The most interesting fintech story of the last two weeks isn't really about fintech. It's about AI agents becoming economic actors. Visa, Mastercard and Ant are already working on how to identify an AI agent and verify what it's allowed to do. The question I'm more interested in comes after verification: who is responsible when an authorised agent makes the wrong decision? That's the theme running through this...