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
This product-description skill is mostly purpose-built, but broad triggers and ambiguous retention disclosures could expose proprietary product or competitor data to an external API unexpectedly.
Install only if you are comfortable sending product details, draft listings, and optional competitor descriptions to YunlvAI's TradeGPT API. Use it for explicit B2B/export product-description tasks, avoid invoking it for generic SEO or marketing conversations, and review local generated output/log folders for retention expectations.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The trigger list contains broad terms such as 'SEO', '差异化', and '产品页面' that can match many ordinary conversations unrelated to this skill's intended scope. Over-broad activation can cause the wrong skill to engage, increasing the chance that sensitive business content, draft copy, or competitor information is sent to the external API unnecessarily.
The skill advertises multilingual generation and translation but does not clearly require the user's language choice or opt-in before producing or sending content for translation. In a skill that may process proprietary product descriptions and competitor data through a third-party API, implicit language handling can lead to unnecessary disclosure, unexpected processing, or output in the wrong language for the user's business context.
The skill states that generated product descriptions are 'not stored, not shared' while also declaring a local storage path for generated outputs and logs. This inconsistency can mislead users and operators about actual data handling, causing accidental retention of proprietary product data, competitive intelligence, or customer-specific content under a false expectation of non-storage.
The trigger list includes broad terms such as "SEO", "差异化", and "product description" that can match many unrelated user requests, increasing the chance this skill is invoked outside its intended scope. Over-broad invocation can route user data or prompts to an external API unnecessarily, causing unintended data exposure, irrelevant tool use, or prompt-surface expansion.
This markdown file contains instructional content exclusively in Chinese, and there is no indication that users may choose another language or that the content is intentionally limited to a Chinese-speaking region or audience. Under the policy, forcing a specific language without user opt-in can be a natural-language policy violation.
This code file includes natural-language descriptions, command help, and output labels that are effectively fixed to Chinese. The policy requires flagging language or locale constraints when the skill forces a specific language without user opt-in, and no alternative language option or justification is provided here.
This markdown file is primarily titled and structured in Chinese, but the reusable user-facing templates are written exclusively in English. That can amount to a language/locale policy issue if the skill implicitly forces English output without user opt-in or an explicit choice.
No suspicious patterns detected.