Security Policy

Belay executes your code against your database; the engine itself holds no credentials beyond the storage URL you give it, and the dashboard/MCP surfaces are operator tools intended for trusted networks. Both are read-only by default when no authority is configured: dashboard writes require token: or authorizer:, and MCP writes require --authorizer or the explicit --allow-mutations opt-in. Bind localhost or front the dashboard with a TLS proxy for remote access.

Reporting a vulnerability

Please do not open a public issue for security reports. Email the maintainer (address on the GitHub profile) with details and a reproduction if possible. You'll get an acknowledgment within a few days; fixes ship as patch releases with credit unless you prefer otherwise.

Scope notes for researchers

• SQL construction: all values are bind parameters; the only interpolations are compile-time field/index names. Reports proving otherwise are very welcome.
• Encrypted inputs are AES-256-GCM envelopes (Belay.Job); keys come from your MFA config and are never persisted or logged by Belay.
• The dashboard's HTTP server is intentionally minimal (no TLS); deployment guidance lives in the operations guide. Mutations require JSON, reject a mismatched browser Origin, cap request bodies at 1 MiB, and reject ambiguous or unsupported request framing. Request headers are capped at 100 fields / 64 KiB. Query-string tokens are accepted for GET/SSE only, never for mutations.