Security

Read-only AI access
to your database

wuup can read your MongoDB, never write to it. Every query passes a guard that blocks writes and server-side JavaScript, returns at most 100 rows and stops after 10 seconds. Here is exactly how, and what stays your job.

write and server-side JavaScript operators blocked in every query
8operators
the most any single query can return
100rows
time limit before a query is stopped
10s

Guarded in code. Private by default.

These limits are enforced on every query, on every plan. None of them is a setting you can forget.

What the guard enforces

Each query is checked before it runs and limited while it runs.

  • Write and JS operators$out, $merge, $whereBlocked
  • Rows per queryUp to 100Capped
  • Query timeout10 secondsEnforced
  • Connection stringsAES-256-GCMEncrypted

What stays out of reach

The model works with the schema and returned rows only. Everything below is kept away from it.

Sensitive fields16 name patterns, at any depthAuto-redacted
Scope
Only collections you pick
System databases
admin, local, config: never
$lookup, $graphLookup, $unionWith
Must stay in scope
Binary fields
Hidden
Your AI key
Masked in the app

How a query is checked

The exact path every MongoDB query takes, in order. If any step fails, the query does not run and the model is told why.

  1. 01OwnershipThe connection must belong to your account. Nobody else's question can reach it.
  2. 02ScopeThe database and collection must be ones you enabled. admin, local, config and system.* are never queryable.
  3. 03GuardOnly allowed read stages pass. Write and server-side JavaScript operators are rejected, and so is any reference to a hidden field. $lookup, $graphLookup, $unionWith must stay in scope.
  4. 04Run with limitsfind or aggregate runs with a 10 second time limit, at most 100 rows and no disk use.maxTimeMS: 10000, limit: 100, allowDiskUse: false
  5. 05RedactHidden fields are removed from every row, at any depth, before anything reaches the model.
  6. 06Cap sizeThe result is trimmed to 50 KB, so a wide collection can't flood the model.
  7. 07RecordThe query is saved with the answer and shown under Queries used, ready to copy.
Rejected at the guardnever runs
db.orders.aggregate([
  { $match: { status: "paid" } },
  { $out: "orders_backup" }
])

$out is not allowed. wuup bridges are read-only and support these stages: $match, $project, $addFields, $set, $unset, $group, $sort, $limit ...

Blocked operators

Rejected wherever they appear in a query.

  • $out
  • $merge
  • $function
  • $accumulator
  • $where
  • $currentOp
  • $listSessions
  • $listLocalSessions

Hidden automatically

Fields whose names match these patterns, at any depth, plus binary fields such as embeddings. You can hide more per collection.

  • password
  • passwd
  • pwd
  • secret
  • token
  • jwt
  • api_key
  • apikey
  • private_key
  • ssn
  • cvv
  • otp
  • salt
  • hash
  • card_number
  • credit_card

What the model sees,
and what it never does

An AI model writes the query and the explanation. Here is the full list of what it is given.

Sent to the model

  • Your questionAnd the conversation so far in that chat.
  • A schema summaryCollection and field names, types and a few sample values from the scan. Never samples of hidden fields.
  • The rows a query returnedUp to 100 rows and 50 KB, with hidden fields already removed.
  • Cited passagesFor documents, the passages that answer the question, numbered as sources.

Never sent

  • Your connection stringIt is decrypted only to run a query and is never part of a prompt.
  • Hidden fieldsRemoved from every row and blocked inside queries, so they can't be filtered or grouped on.
  • Collections you did not scopeOr the admin, local, config databases, which are never queryable.
  • Binary fieldsBlobs such as embeddings are hidden automatically.

Where your data lives

What wuup stores, what it does not, and where your AI key fits in.

  1. 01Your database stays where it iswuup runs queries on demand. It does not copy your collections. The schema scan keeps field names, types and a few sample values, never for hidden fields.
  2. 02Connection strings are encryptedThey are encrypted with AES-256-GCM before they are stored, and decrypted only at the moment a query runs.
  3. 03Answers are saved with your chatsMessages, charts, tables and the queries used are stored with the chat so you can return to them. Delete a chat when you no longer need it.
  4. 04The answering model sees the promptYour question, the schema summary and the returned rows go to the AI provider that writes the answer: Gemini on free questions, or the provider of your own key.

Bring your own key, handled carefully

  • You paste the key once in Settings. wuup checks it by listing your provider's models.
  • It is stored on your account and used only for your own questions.
  • After saving, the app only ever shows a masked version of it.
  • Remove it at any time and wuup stops using it right away.
How bring your own key works

What stays your job

wuup's guard is one lock. These three keep you safe even if something upstream changes.

  1. Connect with a read-only userGive wuup a database user with the read role on one database. It is a second lock that does not depend on wuup.Create a read-only user
  2. Keep network access tightUse your cluster's IP access list and keep it as narrow as your setup allows. Remove connections you no longer use.
  3. Scope the least you needEnable only the collections a question needs, and review the hidden fields for anything else that is sensitive.Is it safe to connect a database to AI?

Security questions,
answered

Read-only by design.
Ready when you are.