Banking

The examples below describe potential use cases. Execution depends on available skills and connectors, customer permissions and qualification in the customer environment.

What the bank is asking for

A quarterly review names four hundred corporate accounts. For each one, someone opens the customer file, the transaction history and the current regulatory requirement, decides whether the review is complete, and writes down why. The list is right; the reasons take three weeks.

• List the accounts whose review is outstanding, with the reason for each and the record that proves it.
• Follow an unusual pattern of transactions through the systems that hold it, and write what was found.
• Compare a new product against the disclosure requirement that applies to it, clause by clause.
• Answer a branch question from the bank’s own procedures rather than from memory.

How the work is done

An agent is a model, a set of approved skills, tools and a policy, applied to a scope.

Agents reach your systems through the MCP servers you connect in the console. A token you enter there is sealed, never shown again, and acts only with the permissions your system gives it; a connector that runs on one of your hosts keeps its token in that host's own connector file.

Execution follows the configured host policy. A command can be approved, denied or referred for human review; individual approval depends on that policy.

Customer-controlled inference and execution boundaries.

Before any of that touches customer data, the bank’s own infrastructure is the safer first workload: the servers behind the channels, the batch jobs and the branch estate. Those questions are how a bank tests whether the controls hold.

Read-only execution policy is the default on every enrolled host; the full policy is an explicit, per-host choice.

Host investigations show the commands that ran, their exit codes and output, per host.

A host joins the fleet with one install command and an enrollment token; revoking the host unpairs it.

Customer-hosted installations support an identity provider through OIDC with PKCE. Hosted workspace SSO must be confirmed for the agreed deployment.

Bring your own model — OpenAI-compatible endpoints, Ollama, Anthropic, or Cloudflare AI Gateway / Workers AI — with keys envelope-encrypted at rest.

Guides for Saudi banks

These guides cover how Saudi banks deploy private AI agents under SAMA CSF, NCA ECC and PDPL:

• Self-hosted LLMs for banks — SAMA CSF requirements and how private AI agents fit.
• PDPL and AI agents — how the Personal Data Protection Law applies to AI agents.
• AI agents and NCA ECC-2:2024 — mapping AcTree’s controls to NCA’s essential cybersecurity controls.