Clear limits for AI actions

Let AI help.
Stay in control.

Choose what your AI helpers can do. Aletheia checks important actions against your rules, asks you when a decision needs your review, and keeps a clear record of what happened.

Start with one AI agent. Add more rules and tools whenever you need them.

Request · documents.read
HumanAI AgentCredentialPermissionToolPolicyTrust DecisionApprovalOutcome
ALLOWCredential valid · permission granted · policy allows

Illustration only. This is not a live security check.

How actions are checked

One request. Every check. A reason you can read.

See what happens when an AI helper asks to do something important.

Actor

A human or an AI agent asks to perform a specific action.

ALLOW

The request satisfies the configured authorization rules.

Demonstration only. Live decisions happen inside your organization's Trust Core.

The problem

Permission is not the same as trust.

Authentication

asks who is acting.

Authorization

asks what they can do.

Aletheia

evaluates whether this specific requested action satisfies your configured trust and authorization rules, right now.

Aletheia does not prove an action is safe or remove all risk. It makes sure every consequential action meets the rules you set, and leaves a record of why.

Trust Graph

Trace the reason behind the decision.

The Trust Graph draws your organization's recorded relationships: who owns which agent, which credential it holds, which tools it can call, and which decisions it triggered. Select any decision and Trace Trust walks the path that led to it, built only from what was recorded.

  1. 01
    HUMAN → OWNS → AGENT
  2. 02
    AGENT → HAS_CREDENTIAL → CREDENTIAL
  3. 03
    AGENT → HAS_PERMISSION → PERMISSION
  4. 04
    AGENT → CAN_INVOKE → MCP TOOL
  5. 05
    ACTION → EVALUATED_BY → POLICY
  6. 06
    TRUST DECISION → REQUIRED_APPROVAL → APPROVAL
  7. 07
    APPROVAL → RESULTED_IN → OUTCOME
MCP & agent permissions · Beta

Give agents boundaries, not blind trust.

Register an MCP server, discover its tools, and grant each agent only the tools it needs. Every tool call is checked by the same Trust Core and its policies, with human approval where required. The remote tool runs only after an ALLOW.

Works with MCP servers reachable over HTTP. Other transports are not supported yet.

  1. 01
    AGENT
    requests a tool call
  2. 02
    MCP SERVER
    registered by your organization
  3. 03
    TOOL
    discovered, with its own risk level
  4. 04
    PERMISSION CHECK
    explicit grant for this agent
  5. 05
    TRUST DECISION
    allow · deny · require approval
Value Layer · Proof-to-Pay

Verify the outcome before value is released.

An agent submits proof against conditions agreed up front. Verification is deterministic: missing or invalid proof fails, and value stays locked. Release always requires a named human approver.

BETA — SIMULATED TEST VALUE ONLY. NOT REAL MONEY.

  1. 01
    AGREEMENT
    task, conditions, test value locked
  2. 02
    CONDITIONS
    e.g. records ≥ 10,000
  3. 03
    AGENT SUBMITS PROOF
    only the assigned agent
  4. 04
    DETERMINISTIC VERIFICATION
    VERIFIED · FAILED · REQUIRES_REVIEW
  5. ×
    INVALID PROOF → FAILED
    value never moves
  6. 06
    HUMAN APPROVAL
    required before release
  7. 07
    SIMULATED RELEASE → LEDGER
    append-only trace
How it works

Start small. Add detail as you go.

  1. 01

    Add an AI agent

    Give the helper a name so you can recognize it in your workspace.

  2. 02

    Choose what it can do

    Allow only the actions it needs. You can change these rules later.

  3. 03

    Review important actions

    See what was allowed, what was stopped, and anything waiting for you.

Make every consequential AI action accountable.

Start with a clear decision. Keep the evidence. Trace the outcome.