bitable

SUSPICIOUS: the functional scope is narrowly aligned with readonly Bitable access, but the required `lark` CLI is not provenance-verified and the documented command/auth syntax appears inconsistent with the official Lark MCP tooling cited in the evidence. Main risk is supply-chain trust in an unverifiable local binary rather than overt malicious behavior or clear credential exfiltration.