Evix LabBook a demo
for agents · MCP

The boundary is the tool set, not the prompt.

Our own model component is the assistant. On this page, “agent” means someone else’s program.

A program acts on a named person’s authority, inside a tool surface built for the circuit it is in. The tools that return findings and assessments are not filtered out of a counterparty’s surface. They are absent from it, and a prompt cannot ask for a tool that was never offered.

evix-tools 2.2.0 · mcp 2026-03-26 · 24 tools across two circuits

Two circuits, two tool surfaces.

  • present in this surface
  • absent — drawn as an absence, like an unestablished fact
Own tenantcircuit 1 · 19 tools present

Your own program, acting on the authority of a named analyst in your tenant.

read, by access key
  • list_cases
  • get_case
  • get_coverage
  • get_claims
  • get_ownership_graph
  • list_entities
  • get_counterparties
  • get_merchant_request
  • get_sources
  • list_documents
  • get_snapshot
ingest · other
  • create_case
  • upload_document
  • recheck_sources
  • recheck_document
  • export_dossier
  • get_profile_options
the two that matter
  • get_findings
  • get_assessment

Present, filled and callable. Your findings are yours.

recording or countersigning a decision has no method name in any circuit — no tool exists for either act
Counterpartycircuit 2 · 5 tools present

Another institution's program, holding an access key you issued. It never sees your case file.

read, by access key
  • get_shared_coverage
  • get_shared_request
  • list_shared_cases
ingest · other
  • open_shared_case
  • open_shared_case_by_id
the two that matter
  • get_findings
  • get_assessment

Absent. Not permitted-and-refused: the tool list this program receives has five entries, and these are not among them. There is no name here for a prompt to call.

tools/list → 5 toolsa call to get_findings returns method not found, because the method does not exist on this surface

The dashed tokens above are drawn in the same vocabulary as an unestablished fact, and for the same reason: they mark the edge of what exists, not something withheld behind a check.

a filter can be misconfigured. an absent method cannot be called.

A person and a counterparty’s program, side by side.

Two kinds of fact live in this table. “Not allowed” is a right withheld from an actor who can see the action exists. “Tool not present” means the action has no name in that surface at all. The whole argument lives in that difference, so the two cells are drawn differently.

What a person may do and what a counterparty’s program may do, with the two kinds of refusal kept apart.
actiona persona counterparty’s program
Read a case and what it is measured byallowedtool not present
Open a caseallowedtool not present
Add documents and factsallowedtool not present
Read the coverage a counterparty exposesallowedallowed
Read a counterparty's findings and assessments—tool not present
Record a decisionallowedtool not present
Countersign a decisionallowedtool not present
Choose a lighter set of requirementsallowednot allowed
“not allowed” is a right withheld and it is refused in words. “tool not present” is an absence, and it is drawn as one.

A program acts on a named person’s authority.

Access is a personal bearer token, issued from the profile page. Every call a program makes is written to the append-only journal under the named person’s authority, and the actor class — program — is recorded separately from the person acting. Revoking the token ends the access; the journal keeps what was done under it.

The tool reference lists every method, its arguments and the circuits it exists in.

evix-tools 2.2.0 · mcp 2026-03-26 · 24 methods · changelog per versionRead the MCP tool reference →

Point your agent at a sandbox tenant.

A sandbox with the demo case, both circuits, and a token you can revoke. Call the tools that are absent and see what comes back.

Book a demoOnboarding is by hand — which is why we do the first case with you.