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 PPAP assistant is a coherent Chinese-language quality-documentation skill with a simple local checker script and no evidence of hidden, persistent, destructive, or exfiltrating behavior.
Install this if you want a Chinese-language PPAP documentation helper. Only run the checker on PPAP JSON files you intend to provide, and review any generated templates or reports against your customer-specific requirements before using them formally.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill references local files and a Python script for checking PPAP inputs, which implies file read capabilities and potentially file output/report generation, but it does not declare any explicit tool scope or permissions. This creates an authorization ambiguity where an agent may access files more broadly than intended, increasing the risk of unintended data exposure or misuse when handling user-supplied paths or documents.
The trigger conditions include broad terms like PPAP, submission warrant, part approval, and IATF16949, which may match loosely related quality-management conversations. Over-broad activation can cause the wrong skill to engage, leading to unnecessary file access, inappropriate guidance, or processing of unrelated user documents under this skill's workflow.
The title and entire guidance are written exclusively in Chinese, and the file provides no indication that users may choose another language or that the language restriction is required for a region-specific or compliance-specific purpose. Under the policy, forcing a specific language without opt-in is a natural-language policy violation.
This markdown file contains user-facing instructional content only in Chinese, with no indication that users may choose another language or that the skill is explicitly scoped to Chinese-speaking users. Under the policy rule for language/locale constraints, forcing a specific language without opt-in can be a natural-language policy violation.
This code file contains user-facing natural-language descriptions and output messages in Chinese only, starting with the module docstring and continuing throughout the CLI. Under the policy rule for language/locale, forcing a single language without user opt-in can be a natural-language policy violation unless clearly justified as region-specific.
No suspicious patterns detected.