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
Security
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.
These limits are enforced on every query, on every plan. None of them is a setting you can forget.
Each query is checked before it runs and limited while it runs.
The model works with the schema and returned rows only. Everything below is kept away from it.
The exact path every MongoDB query takes, in order. If any step fails, the query does not run and the model is told why.
maxTimeMS: 10000, limit: 100, allowDiskUse: falsedb.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.
Hidden automatically
Fields whose names match these patterns, at any depth, plus binary fields such as embeddings. You can hide more per collection.
An AI model writes the query and the explanation. Here is the full list of what it is given.
Sent to the model
Never sent
What wuup stores, what it does not, and where your AI key fits in.
wuup's guard is one lock. These three keep you safe even if something upstream changes.
No. The query guard rejects any pipeline that uses $out, $merge, $function, $accumulator, $where, $currentOp, $listSessions, $listLocalSessions. wuup only calls find and aggregate. A read-only database user adds a second lock that does not depend on wuup.
Any field whose name matches password, passwd, pwd, secret, token, jwt, api_key, apikey and similar patterns is removed at every depth before results reach the model. Binary fields, such as embeddings, are hidden too.
Connection details are encrypted with AES-256-GCM before they are written to the database, and decrypted only when a query runs.
No. Queries can only target the collections you scope. Stages that reach other collections, such as $lookup, $graphLookup, $unionWith, must point at an in-scope collection in the same database. The admin, local, config databases are never queryable.