Security audit
Security checks for vulnerabilities and agentic risk
This skill is a disclosed Lark contact lookup helper, but users should treat employee profile results as permission-scoped workplace personal data.
Install only if you are comfortable letting the agent query Lark directory data available to your user account. Use it for legitimate workplace tasks, confirm ambiguous people before sending messages or invites, and avoid broad filter-only searches unless you have a valid business reason.
This markdown file advertises resolving employees by name/email and reverse-looking up a person's name, department, email, and contact information. Because this behavior exposes potentially sensitive personnel data, the description should warn that results depend on permissions and should only be used for authorized work purposes, but no such user-facing warning appears here.
The documentation materially broadens the skill from a narrow identifier-resolution helper into a richer employee directory/profile lookup tool, including complete-profile retrieval via --user-ids. In an agent setting, that expands access to organizational personal data beyond the stated purpose, increasing the chance of over-collection, unintended disclosure, and misuse by downstream workflows.
Allowing filter-only use such as listing all chatted or departed employees turns a resolver into a directory-enumeration primitive. Even without auto-pagination, this enables systematic harvesting of employee metadata in batches and can expose sensitive organizational information unrelated to the user’s immediate task.
The examples present the command as able to '列出所有' employees matching certain filters, which implies a complete listing behavior. Later, the notes explicitly state that the command does not auto-paginate and that has_more=true requires query refinement, so the documented usage overpromises completeness relative to the stated behavior.
No suspicious patterns detected.
