Tp2
- Category
- MCP Tool Poisoning
- Confidence
- 85% confidence
- Finding
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
- Content
Security audit
Security checks for vulnerabilities and agentic risk
The skill appears to be a GitHub automation helper, but its token use and broad repository actions are not scoped clearly enough for automatic trust.
Review before installing. Use a least-privilege GitHub token, preferably limited to specific repositories, and require explicit confirmation before any action that merges code, changes Issues or PRs, triggers workflows, deletes branches, or publishes releases. Treat the 'no API key' metadata claim as inaccurate because the skill says it needs GITHUB_TOKEN.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The manifest advertises broad automation over PRs, Issues, CI/CD, and releases but does not disclose operational boundaries, approval requirements, or potentially destructive repository actions. In a GitHub-management skill, this omission is risky because users may grant broad trust to actions that can merge code, alter workflows, publish releases, or otherwise affect repository integrity.
The visible skill name and description are written only in Chinese, with no indication that users may choose another language or that the skill is intended for a Chinese-only audience. This can be a natural-language policy concern when a skill appears to impose a locale without opt-in or documented regional justification.