Check the workspace for leakage without scoring
check_leakageRuns integrity checks without spending a reveal, detecting train/sealed overlap, code leakage or tampering, and files containing hidden canary labels; optionally limit code checks to specific paths.
Instructions
Run the integrity checks without spending a reveal.
Reports overlap between the sealed split and train (HV-ROW), leakage and tampering patterns in
the workspace's Python files and notebooks (HV-COD), and data files carrying the hidden canary
labels (HV-CAN-001). paths limits the code checks to some files or folders.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"dataset": "<dataset>"
},
"name": "check_leakage"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| paths | No | ||
| dataset | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| dataset | Yes | ||
| message | Yes | Plain-English summary | |
| blocking | Yes | Findings that would refuse a score | |
| findings | No | ||
| unparsed | No | Files that could not be parsed | |
| warnings | Yes | ||
| files_scanned | Yes | Python files and notebooks analysed | |
| tables_scanned | Yes | Data files compared against the hidden canary labels |