Security and tenant isolation hardening
Environment secrets, MCP permissions, embedded account routes and tenant resources now have additional authorization and isolation checks.
This release adds another layer of protection across account access, deployments and the control plane:
- Read-only members now see environment variable values fully masked. Members who can manage variables can still use the final characters to identify a configured secret.
- MCP write tools enforce the member’s current role as well as the token scope, matching the permissions of the corresponding API routes.
- The authentication embed proxy now rejects traversal and encoded-path attempts before forwarding a request.
- Deployments check the ownership of existing workload, secret and volume names and fail closed if a resource belongs to another organization.
- Error reporting removes credential-shaped values and request query strings before sending an event.
- Organization-scoped request, command and realtime connection limits protect shared control-plane capacity without changing normal dashboard use or scheduled jobs.
The automated security suite now covers cross-organization access, role boundaries and API-token attack paths.