Function skip_for_admin_recovery 

pub fn skip_for_admin_recovery(sql: &str, is_admin: bool) -> bool

The primary escape hatch: the deny-list check is skipped when the caller can reach the admin functions at all – the same predicate register_lakehouse_functions gates deny_queries/remove_query_denial on – and the statement mentions one of deny_queries / remove_query_denial / list_query_denials: three contains checks over the lowercased SQL text, nothing more. No call-position or token analysis: this only ever runs for a query that is already being denied, and the gate it sits behind means any caller it opens for could call those three functions directly anyway.