Access
Permission profile per token
Each token (an access key) carries a permission profile: which databases, which views, which tools, which fields.
SECURITY AND CONTROL
DraftDomMCP: you decide what the AI may do.
Not every AI needs to be allowed to do everything. DomMCP provides clearly defined Domino tools. You decide which databases, views, tools and fields an access may use.
SECURITY
Controlled instead of a black box
Not every AI needs to be allowed to do everything.
DomMCP provides clearly defined Domino tools. This lets you specify which capabilities apply to an area of use.
An environment can, for example, be authorised exclusively for analysis and read access, while developers receive additional development functions and administrators receive more extensive operations functions.
This way, AI can be used where it really brings benefit, without giving it every technical possibility across the board.
SIX BUILDING BLOCKS
How DomMCP secures control.
You decide what the AI may access.
Identity
Access as a Domino user
If you wish, every access runs as a Domino user. Then that user's ACL (the database's access control list) applies, including reader fields.
Writing
Separate from reading
Write access is separate from reading and can be authorised individually. A snapshot is created before every design change.
Traceability
Audit database
Every call lands in an audit database, chained via checksums. Later changes are detected.
Safeguards
Your own rules as policy
Maintenance windows, locked databases and four-eyes approval for change sets.
Data storage
Runs on your server
DomMCP runs on your Domino server. Authorised content goes to the connected assistant. The choice of model and the configuration determine whether data leaves your company.
ATTITUDE
Who holds the reins?
The question is not whether AI will touch your applications, but who sets the direction.
The developer rides the AI.
Control
The developer sets the direction, the AI sets the pace. Permissions are defined, every step is logged, and design snapshots make restoring easier.
The AI rides the developer.
Loss of control
Full access, no logging, no way back. And afterwards nobody can explain why the production database contains what it contains.
DATA AND OPERATIONS
Your data, your server, your choice of model.
This section applies to running DomMCP on your own Domino server (sovereignty package). For the DMaaS services, the contract governs processing, location and deletion periods.
The choice of model and the configuration determine whether data leaves your company. If nothing is to go outside, DomMCP also works with a model that is run inside your company. For fully internal processing, the model must be operated and configured accordingly.
Read access requires no changes to the design of your application. For console commands (Enterprise edition), read commands are included and commands that modify are blocked.
Which functions are available depends on the edition. The overview is on the “DomMCP” page.
FAQ
Questions and answers
What may the AI do with DomMCP?
You define what the AI may do through a permission profile. Each token (an access key) carries a permission profile: which databases, which views, which tools, which fields. Reading and writing are separate and can be authorised individually.
Can I trace what the AI has done?
Yes. Every call is recorded in an audit database, chained via checksums. Any later change to the entries is detected.
Do my permissions in Domino also apply to the AI?
If you wish, every access runs as a Domino user. Then that user's ACL (the database's access control list) applies, including reader fields.
Does my data leave the company?
DomMCP runs on your Domino server. Authorised content goes to the connected assistant. The choice of model and the configuration determine whether data leaves your company. DomMCP also works with a model that is run inside your company.
Can design changes be undone?
A snapshot is created before every design change. It captures the previous state and allows a targeted restore.
On your own Domino server.
With the sovereignty package you run DomMCP on your own Domino server, with licence and guided setup. Licences, setup and optional workshop on request.