Overview
Authentication and user management for applications. Agents use it live through governed tools, and the underlying records stay in Clerk.
What Modus reads
- 1Connection
Accessed live on demand through governed agent tools — nothing is bulk-copied or stored outside the session.
Liveon-demand reads
7agent tool groups
1connection method
1security controls
Common use cases
- 01
Answer who has access from Clerk, scoped to the directories you connect.
- 02
Keep identity reads on a dedicated credential.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
API token
A token you create in the source and paste into Modus. Agents never see it.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Write approval
Actions that change state in the source system are marked as writes and require an explicit human confirmation before they run.