Security

Last updated: June 13, 2026

StackBridge exists to let AI act on your tools safely. Security isn’t a feature bolted on top — it’s the product. Here is how we protect your credentials, your data, and the actions your agents take.

Secret vault

• API keys and OAuth tokens are sealed with AES-256-GCM using a server-only encryption key, with a key-version field reserved for rotation.
• Secrets are decrypted only in memory, at the moment a tool runs. They are never returned to the browser and never written to logs.
• The plaintext value is shown once when you add it (if at all) and never again.

Safe outbound execution

Every tool call goes through one hardened execution path:

• SSRF protection — the target URL is parsed and validated: http(s) only, a port allowlist, and DNS resolution with every resolved IP classified. Private, loopback, link-local, and cloud-metadata addresses (e.g. 169.254.169.254) are blocked.
• DNS-rebind & redirect safety — the connection is pinned to the already-validated IP, and redirects are followed manually with each hop re-validated, so a 302 can’t bounce a request to an internal address.
• Timeouts & size caps — every call has a deadline and a streamed response-size limit, so a slow or huge response can’t hang or exhaust the worker.

Governance & approvals

• Each tool carries a risk tier. Read-only calls can run automatically; anything that writes, sends, or deletes can require explicit human approval.
• Approvals happen out of the request path — a risky action pauses with a preview of exactly what it will do, and only runs once you approve it.
• Every call is logged with its outcome, status, and duration for a complete audit trail.

Redaction

Before anything is logged, known secret headers, token patterns, and the exact secret values injected for that call are redacted. There is no code path that writes a raw credential to the database.

Isolation

Data is scoped per workspace. Server-side queries are funneled through a workspace-scoped data layer that applies the workspace filter on every read and write, so one tenant cannot reach another’s tools, secrets, or logs.

Authentication

• Passwords are hashed with scrypt; sessions ride in an httpOnly cookie.
• The hosted MCP endpoint authenticates with a bearer token stored only as a hash, compared in constant time, and rotatable with a short grace window.
• OAuth connections use PKCE and an HMAC-signed, cookie-bound state to prevent CSRF; the resulting tokens go straight into the vault.

Your keys, your control

StackBridge is bring-your-own-keys. Your credentials are used only to make the calls you configure, under the approval rules you set, and you can revoke any key or disconnect any account at any time.

Reporting an issue

Found a vulnerability? Please email seyficembaskin@gmail.com. We appreciate responsible disclosure.