Does FutureSmart Database Agent withhold an excluded column when asked for it by name?
FutureSmart Database Agent could not be executed for this scenario because it cannot exclude a single column. Its only exclusion control works on whole tables on both connections, and no other settings screen offers column-level control. No question was asked, so the agent's handling of a direct request for an excluded column was not observed.
1 of 1 test case failed
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 column asked for directlyFailEvidence
We did not send a question because the product has no way to exclude a single column.
There is no applicable tool response to show for this step.
| ✗ | Expected: The excluded column should be unavailable, with no values shown.Found: The product offers no way to exclude a single column; its only exclusion control switches off a whole table, so the scenario could not be executed and no question was asked. |
It is Fail because the product lacks the single-column exclusion the scenario needs, so the scenario could not be executed. Its only exclusion control works on whole tables, and no question was asked, so how it answers a direct request for an excluded column was not observed.
Whole-table switch. Turning off 'returns' excludes the whole table, while the other tables stay included.
Matching connections. Both connected databases show the same static '0 columns' label on every table.
Description samples columns. The description generator says it samples tables, columns and a few rows, but offers no per-column control.
Freshness marker. No version string appears; the closest freshness marker is the auto-generated description timestamp.
A still image cannot show whether the '0 columns' label opens a column list.
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 column is asked for directly → | |
| Tool | FutureSmart Database Agent → |
Global scenario definition → · Global capability definition → · FutureSmart Database Agent 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.