Security

Security is the reason to put OneQuery between agents and production data. These pages explain what OneQuery is meant to control, what still belongs to operators, and how to avoid turning prompts into the only access boundary.

Security architecture Credential flow, source execution, gateway placement, and audit boundaries.

Threat model What OneQuery helps protect against and what it does not claim to solve.

Data handling How to reason about credentials, result payloads, logs, and support sharing.

Cost limits Use budgets, query shape, and provider controls to keep agent requests bounded.

Security Principle

OneQuery should be the deterministic boundary. The agent prompt should explain the workflow, but source credentials, source permissions, query validation, result limits, and audit review should live outside the prompt.