Security is the product.
LockMCP exists to make agent access safe. Encryption, tenant isolation, least-privilege access, controlled egress, and a complete audit trail are core to how it works.
Our security controls
Encryption at rest
Upstream credentials and signing keys are protected with AES-256-GCM; keys are rotated.
Encryption in transit
All traffic to and from the service uses TLS.
Tenant isolation
Postgres row-level security scopes every data-plane query to the active tenant.
Least privilege
RBAC governs dashboard access and which tools each identity can call.
Egress protection
SSRF validation blocks loopback, link-local, and private-range destinations on outbound calls.
Immutable audit
Identity-attributed, append-only logs of every tool list and call.
Fail-closed revocation
Sessions can be revoked instantly; the data plane denies on uncertainty.
No secrets in clients
Agents present verifiable identity; upstream secrets never leave the hub.
Tenant isolation
Row-level security scopes every data-plane query to the active tenant.
Reporting a vulnerability
We welcome responsible disclosure. If you believe you’ve found a security issue, email security@lockmcp.com with details and steps to reproduce, and we’ll respond promptly.
For compliance documentation and our current sub-processor list, visit the Trust center.