Home / Platform / Identity and access
Platform · Identity
Know exactly who, and what, is calling.
Every AI tool call is tied to a real person and the agent acting for them, using the identity provider you already run.
| Person | Acting through | Tool | Tool sees |
|---|---|---|---|
| Anna K. | Coding agent | github.create_issue | anna.k |
| Tom R. | Sales assistant | crm.read_account | tom.r |
| Priya S. | Finance agent | erp.read_invoice | priya.s |
| Unknown | Unregistered agent | files.read | Blocked |
Illustrative interface
Bring your own identity provider.
Works with any standard single sign-on provider (OIDC). No new user directory to manage, and leavers lose AI tool access the moment their account is switched off.
Illustrative interface
Tools see the user, not a shared account.
RimSift passes the user's identity to the tool, so GitHub or Slack logs show the real person behind each action, and the agent acting for them.
Without RimSift
svc-ai-bot created issue #482
Who asked? Unknown.
With RimSift
anna.k via Coding agent created issue #482
Traceable to a person and an agent.
Illustrative interface
No keys on laptops.
API keys and tool credentials are held centrally and added on the way out. Rotate or revoke once, everywhere.
| Tool | Where the key lives | Status |
|---|---|---|
github | Held by RimSift | Rotated 3d ago |
crm | Held by RimSift | Rotated 9d ago |
slack | Held by RimSift | Rotated 1d ago |
Illustrative interface
What it protects against
Stop agents acting as nobody.
Maps to OWASP MCP Top 10: MCP01 token and secret exposure, MCP07 weak authentication and authorisation.
See every AI tool call your organisation makes.
A 30-minute demo with our engineers, on the AI tools you already use.