Connect

MCP gives the AI connectivity. ai4bp gives it authority.

MCP, the Model Context Protocol, is a standard way for a program to offer its tools to an AI, such as a document store, email, a calendar or a core banking system. ai4bp reaches the systems you already run through MCP, and every call goes through its gateway before it happens.

Try the demo See a call traced

Connectors / Harbor Legal, Lemon law · Westland 4 attached

VyxloMCP server vyxlo

Stores documents, reads them and extracts fields.
- vyxlo.get_documentRead only
- vyxlo.extract_fieldsRead only
- vyxlo.store_documentInternal, no approval
EmailMCP server email

Sends and tracks outgoing email.
- email.sendOutbound gate, lawyer approval
CalendarMCP server calendar

Creates deadlines and follow-ups.
- calendar.create_eventInternal, no approval
E-signatureMCP server esign

Collects signatures on agreements.
- esign.requestOutbound gate, lawyer approval
Bank coreThe core’s own MCP server

For the banking pack, not in the lemon-law demo. Exposes the core’s BIAN service operations.

Customer OfferParty Reference Data DirectoryCustomer Credit RatingConsumer LoanPayment Execution

6 tools on the approved menu. A step can call only what the released package lists, and each call is governed by its kind.

1 / The gateway

No agent calls a tool directly.

Every call goes through ai4bp’s gateway. It checks that the call is on the package’s approved action menu, runs the rules and the clause checks, collects any approval needed, then makes the call and checks the outcome. An uncertain result is reconciled before anything is tried again.

Gateway / call trace LL-2047

calendar.create_event Norvik’s response deadline, step 4

JSON in

{
  "calendar": "harbor-legal-cases",
  "title": "Norvik Motors response due, LL-2047",
  "date": "2026-11-25"
}

Gate checks

On the approved action menupass
Rule response_due, WLL §6(a)pass
Approval, not needed for an internal callpass
Event createdaccepted by the calendar
Outcome checked against the calendarverified

JSON out

{
  "event_id": "evt-0002",
  "status": "created"
}

The notice itself leaves the same way, as email.send after a lawyer approves it. See that trace on the Run page.

2 / Three kinds of call

The more a call can change, the more it needs.

Reading a document changes nothing. A date on your own calendar stays inside the firm. A letter or a signature request reaches someone outside, so it waits at the outbound gate for a lawyer. The package sets the kind for each of its automation points.

Process / Automation points, v0.1 9 points

Nine automation points 2 read only, 4 internal, 3 through the outbound gate.
Step	What it does	Tool	How it is governed
1 Intake	Send the fee agreement for signature	esign.request	Outbound gate, lawyer approval
2 Collect documents	Ask the dealer for repair orders	email.send	Outbound gate, lawyer approval
2 Collect documents	Read a repair order into fields	vyxlo.extract_fields	Read only
2 Collect documents	Put the dealer chase on the calendar	calendar.create_event	Internal, no approval
4 Send written notice	Find the manufacturer’s designated address	vyxlo.get_document	Read only
4 Send written notice	Send the notice	email.send	Outbound gate, lawyer approval
4 Send written notice	Put the response deadline on the calendar	calendar.create_event	Internal, no approval
5 Final repair attempt	Put the final repair window on the calendar	calendar.create_event	Internal, no approval
8 Close	Archive the closed file	vyxlo.store_document	Internal, no approval

The AI can stop, but cannot release. Only an exact rule or a person lets a call through.
No approval is ever made by the AI alone.

3 / ai4bp as an MCP server

Agents you did not build send their outgoing actions here first.

ai4bp is also an MCP server. Another agent in your organization, one ai4bp does not run, asks ai4bp’s tool to check an action before it goes. The answer is allow, or hold with the clauses. Here an agent’s purchase order is held.

Gateway / Harbor Legal purchasing policy ai4bp MCP server

ai4bp.check_action a purchase order, from an agent ai4bp does not run held

JSON in

{
  "agent": "office-purchasing-agent",
  "action": "send purchase order",
  "order": "PO-3318",
  "supplier": "Quillmark Supplies",
  "to": "orders@quillmark-supplies.example",
  "total": "$3,180.00"
}

Gate checks

Rulespass
Supplier, Policy PP-3held
Release to the agentnot run

JSON out

{
  "answer": "hold",
  "clauses": ["Policy PP-3"],
  "reason": "Quillmark Supplies is not on the approved supplier list",
  "released": false
}

Nothing was sent. The agent gets the hold and the reason. The hold becomes an exception: adding Quillmark to the approved list changes a control, so the control owner decides.

The firm’s purchasing policy ships as a policy pack: organization-wide rules that belong to no one process, reviewed and released on the same two-checklist screen as any package.
The first release checks what ai4bp’s own processes send, and anything another system or agent asks it to check first. An inline gateway comes later.

4 / Documents through Vyxlo

Every value keeps the line it was read from.

Vyxlo is the document connector. It stores documents, reads them with OCR and extracts their fields as JSON. ai4bp’s AI interprets the fields and the rules decide on them, so a reviewer can check any value against its source.

Repair order BW-48213 is the first of Dana’s three. Vyxlo read all three on 28 October.
vyxlo.get_document finds the owner’s manual, with the page and the quoted line, that fixes a notice held for its address.

Documents / Repair order BW-48213 vyxlo.extract_fields

RO-BW-48213.pdf

Brightwater Norvik

REPAIR ORDER No. BW-48213
Date received: 02 MAR 2026
Date returned: 08 MAR 2026
Odometer in: 6,240
System: TRANS (transmission)
CUSTOMER STATES: vehicle shudders and hesitates when shifting from 2nd to 3rd gear
CORRECTION: updated transmission control software, checked fluid level, road test OK

Fields read by Vyxlo, 28 Oct 2026

Repair orderBW-48213line 1
Date in2 Mar 2026line 2
Date out8 Mar 2026 (6 days)line 3
Mileage in6,240line 4
SystemTransmissionline 5
ComplaintShudders and hesitates shifting from 2nd to 3rd gearline 6
Work doneUpdated transmission software, checked fluidline 7

Read only. Nothing in the document is changed, and no approval is needed.

Approved action menu / Personal loan BIAN core

All five are on the menu. The core exposes other service operations through MCP too.

The same gateway. Each call is checked against the menu and the bank’s policies, approved where the pack says so, then verified.

5 / A bank’s core

Your core is a connector too.

For a bank, the connector is the core system. The action menu is the set of BIAN service operations the core exposes through MCP, such as Customer Offer, Consumer Loan and Payment Execution.

A banking pack needs a BIAN core, or a mock of one, and the bank’s own policies.
ai4bp does not replace your core, your document system or your email. It connects to them through MCP.

See the banking pack

Try it

Watch a call held, fixed and sent.

In the demo, see the notice held at the gate, fix its address from the owner’s manual in Vyxlo, approve it as the lawyer, and follow the email call that sends it.

Try the demo Knowledge packs