Encrypted credential vault
Every stored secret is encrypted at rest with AES-256-GCM. Employees never see or handle a key — credentials live in the vault, nowhere else.
Security
Security isn't a feature here. It's the product.
Toolshed exists because stray API keys are indefensible. So the bar we hold ourselves to is simple: the gateway must be safer than every workaround it replaces.
Hashed, user-bound tokens
API tokens are stored as SHA-256 hashes and are bound to one user and one organisation. A token is only valid while that membership exists.
Microsoft Entra ID SSO
Browser access runs through your existing Entra ID tenant via OpenID Connect — no new accounts, no new passwords, MFA via your Conditional Access policies.
OAuth 2.1 + PKCE for AI clients
MCP clients like Claude authenticate through a standards-based OAuth 2.1 authorization-code flow with PKCE, with Toolshed acting as the authorization server.
Permissions per organisation and team
Owner, admin, and member roles at organisation level; teams decide which integrations each person can reach. Credentials never cross organisation boundaries.
Read-only database policy
Database access is enforced read-only by a SQL policy — single-statement SELECT queries inside a read-only transaction. AI can look, never touch.
Telemetry per tool call
Every tool call is recorded in the usage dashboard: which integration, which user, when. Provable control for auditors and clients.
One gateway, one place to audit
All AI traffic flows through a single authenticated endpoint. No scattered connections to inventory — one place to review, one switch to turn off.
Identity & access
Built to follow your directory
Access rules shouldn't be copied into yet another admin panel — they should come from the identity platform you already govern.
Available
Microsoft Entra ID SSO
OpenID Connect against your own tenant. MFA and Conditional Access policies apply automatically to every sign-in — nothing to configure twice.
Coming soon
Conditional Access group mapping
Assign team access from Microsoft Entra security groups, so AI permissions follow the same groups your Conditional Access policies already govern — a hard requirement we hear from government IT.
Coming soon
Google Workspace
Google SSO with Google Groups as the access-group equivalent, for organisations outside the Microsoft stack.
Aqqo is ISO 27001 certified
Evidence for your auditor, not just promises
You're trusting a vendor with access to your most sensitive systems — so that vendor should meet the same standard your clients hold you to. Aqqo is ISO 27001 certified, and Toolshed makes the access controls in your own ISO, GDPR, BIO, or NIS2 story provable instead of aspirational.
This is the difference between “we trust our people” and a demonstrably controlled process.
| Control | ISO/IEC 27001:2022 | How Toolshed answers it |
|---|---|---|
| A.5.15 | Access control | Access per organisation and team, based on roles |
| A.5.16 | Identity management | One identity via Microsoft Entra ID — no separate accounts |
| A.5.17 | Authentication information | Keys in an AES-256 vault, tokens hashed, never handed to users |
| A.5.18 | Access rights | Granted and revoked centrally; leaving means instant loss of access |
| A.8.15 | Logging | Telemetry per tool call in the usage dashboard |
The offboarding test
Ask any vendor one question: what happens to AI access the day someone leaves?
Stray keys
Keys on personal accounts survive every offboarding checklist. Nobody knows which ones exist, so nobody revokes them — roughly 70% of leaked credentials are still valid years later. The access of an ex-employee simply never expires.
With Toolshed
Disable the SSO account — the step your offboarding already includes — and every AI connection closes with it. Tokens are user-bound, sessions end, and the dashboard shows the access is gone.
Questions from your IT partner or auditor?
We're happy to walk through the architecture, the encryption model, and the audit trail — with your MSP or security reviewer at the table.