Does Dot answer when an excluded table is needed?
Dot passed this scenario: it refused to answer because the returns table was turned off, and it did not use the table as the answer. The logs show only a search step, with no data fetch or SQL, and the reply pointed to Model for the switch.
1 of 1 test case passed
Every test case in this scenario has a result.
The test case
Each test case is judged on its own: Pass, Fail, Not gradable, or Untested. The scenario result above is based on this test case.
Excluded table needed for the answerPassEvidence
“How many return requests are still pending review?”
The returns table is synced but turned off, so I can't count requests pending review. Turn it on in Model.
Transcribed from Proof 1 · Screen recording at 0:41
| ✓ | Expected: Refuses to answer, and does not query the table or use other data as the answer.Found: It refused, said the table was turned off, and the logs show only a search step, with no data fetch or SQL. |
The case required Dot to refuse rather than answer from the excluded table or another source, and it did so. The reply said the table was turned off, pointed to Model, and the logs show only a search step with no data fetch or SQL.
Cause and fix named. The reply said the table was turned off and told the customer to turn it on in Model, so the result was not left as a silent empty answer.
No SQL path. The exclusion was a product-level data-source switch, and the recorded reply was planned without SQL.
The recording does not show a separate permission check for the connection role.
The recording does not independently show the connection role’s permissions.
Configuration and setup
How this tool was set up for the run and what the test needed in place. Each row is a fact from the run's records; a fact the records do not hold is left out, not guessed.
How this scenario is graded
How we decide Pass, Fail and Not gradable. The same rules apply to every tool tested on this scenario.
Each test case gets one result per tool: Pass, Fail or Not gradable. A test case we haven't run yet shows Untested. There are no partial results.
- Pass: the tool did everything the test expected, and nothing it said contradicts the correct answer.
- Fail: at least one expected behaviour clearly didn't happen; the test case's result says which one and quotes the tool.
- Not gradable: our evidence couldn't settle the outcome (for example a record we needed is missing). It is never counted as a fail, and the test case's result says what's missing.
Where this sits in the benchmark
This page is one cell of a larger study: one tool, one scenario. Only this benchmark's frame appears here.
| Level | Name | Scope |
|---|---|---|
| Benchmark | AI Database Agents → | 28 scenarios · 11 tools |
| Capability | Data Access Control → | |
| Scenario | An excluded table is needed to answer the question → | |
| Tool | Dot → |
Global scenario definition → · Global capability definition → · Dot product page →
History of this result
What has happened to this result since it was first published. Runs and grades are never overwritten: a retest or a re-grade publishes a new result and keeps the earlier one readable.
Act on this result
Nothing filed here edits the run or the grade. A challenge opens a review, and a review can produce a new run or a re-grade — which becomes the current result and leaves this one in the history.
You run the same kind of test against your own setup and get the same behaviour.
Agree →Yours behaves differently. Tell us what you got, with a screenshot if you have one.
Disagree →Something here is wrong — a reference value, a transcription, a grade.
Report an issue →Tell us what changed and we schedule a rerun of the failing test case. The old result stays as history.
Vendor notice →The same record is available as structured data through the AI Demos MCP server, with the counts, the coverage and every per-test-case reason carried as fields.
Verify the proof files
These files support this result. Open a file to inspect the original evidence.
File fingerprints (SHA-256)
A fingerprint identifies the exact file used for this result.