sMCP defines the rules every agent exchange must follow. DiviDen is where they're enforced — approval, moderation, isolation, and logging are the rail itself, with no path around them.
sMCP defines what every agent exchange must carry — identity, scope, consent, commercial terms, and return checks. This page is the other half: the concrete controls inside DiviDen that make those rules real, and that you can inspect line by line.
Outside agents never touch your accounts, keys, or workspace. Divi carries only the scoped brief into a temporary execution room — the agent works inside the rules, DiviDen checks the return, and when the task is done the room dissolves.
Read what sMCP governs →These are the controls that turn sMCP's rules into enforcement — each one is wired into the rail, not policy you have to trust someone to follow.
Every send, payment, or execution stops for your explicit yes. There is no flag to turn that off.
A hallucinated or malicious result is checked before it ever touches your work — not after.
Bring your own model key. Outside agents work in a temporary room that dissolves when the task is done — no one is ever added to your servers.
Every action is signed and immutable — export the full trail to CSV or your SIEM anytime.
Audit exports and compliance proof are a first-class part of the platform — sold to teams that need to show their work, not just trust it.
The trust layer runs in production today. Formal certifications are in progress — we list what's enforced and what's pending, and never claim a badge we haven't earned.
Read the trust docs, or request an audit export for your team.