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 is a coherent Feishu project-management workflow, but it tells agents to run mutating shell commands against shared project systems without clear confirmation, scoping, or rollback guidance.
Install only if you control the referenced Feishu workspace/Base and the local venus-bitable-sync.py script. Before running the mutating commands, verify the script contents, confirm the target group/Base, back up the Base or test on a copy, and require explicit approval for setup, sync, seed, collect, track, and migration steps.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
## 必须先读
- `workspace/skills/venus-tracker/SKILL.md`
- `workspace/.planning/venus-erp/task_plan.md`
- 若要约束开发描述质量,同时参考 `workspace/skills/karpathy-coding-guidelines/SKILL.md`
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
- `workspace/skills/venus-tracker/SKILL.md`
- `workspace/.planning/venus-erp/task_plan.md`
- 若要约束开发描述质量,同时参考 `workspace/skills/karpathy-coding-guidelines/SKILL.md`
## 工作流
The skill instructs the agent to run mutating shell commands such as setup-group-tab, sync-roster, and seed-planning without an explicit safety warning or approval checkpoint. Because the skill has shell access and is marked mutating=true, an operator or agent following the workflow could modify live Feishu group state and planning files unintentionally, causing unauthorized changes or operational disruption.
The documented migrate-base command appears to alter an existing live Base schema or data but is presented as a normal step with no caution, backup requirement, or confirmation gate. In a production project-management context, schema migration against a shared Base can corrupt records, break integrations, or impact all users relying on the tracking workflow.