Run safety check
scanRun Tofu’s safety check on this project through the shared backend. The result’s coverage and verdict describe the scope of the pre-deploy tripwire plus a fixed set of deterministic rules over the files Tofu holds for the project. It matches the malware shapes it knows — obfuscated execution, install-time downloads, secret exfiltration, wallet draining, clone-time hooks, curated bad dependency versions — and NOTHING MORE, so pass: true never means the code is safe. coverage states how many files were read of how many were given, which checks ran, and what none of them looks for; verdict says the same in one sentence. pass: true with coverage.inspected: 0 means nothing was inspected, which is not a pass. This result is not a security clearance, and pass is not a statement that the code is safe. mobileReadiness is static metadata, not a safety or device verdict.
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": {
"projectId": "<projectId>"
},
"name": "scan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pass | Yes | ||
| verdict | No | ||
| coverage | No | ||
| findings | Yes | ||
| scannedFiles | Yes | ||
| mobileReadiness | No |