explain_finding
Retrieve the meaning, risk, fix steps with example SQL, and related findings for an Airlock finding kind from an audit result.
Instructions
Explain what an Airlock finding kind means, why it is dangerous, how to fix it (with example SQL), and which other findings are related. Pure lookup — no database connection needed. Use this after get_findings or audit_supabase_rls to understand a specific finding before fixing it. Supported kinds: rls_disabled, permissive_true, anon_unscoped, authenticated_unscoped, write_unchecked, write_unscoped, update_using_unscoped, delete_unscoped, or_branch_unscoped, helper_scoped, policy_trusts_user_metadata, security_definer, anon_executes_definer, definer_search_path_mutable, view_bypasses_rls, matview_exposed, public_bucket, realtime_exposure, default_privileges_to_api_roles, bypassrls_role, owner_bypasses_rls, cross_tenant_read_leak, cross_tenant_write_leak, cross_tenant_delete_leak, service_role_exposed, env_file_exposed, git_exposed, source_map_exposed, scan_truncated, plus any storage_ variant.
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": {
"finding_kind": "<finding_kind>"
},
"name": "explain_finding"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| finding_kind | Yes | The finding kind string from an audit result (e.g. 'rls_disabled', 'permissive_true', 'cross_tenant_read_leak'). |