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 is a straightforward hosted image-upscaling skill, but users should know their images and API key are sent to the provider's external server.
Install only if you trust the image-upscaling provider. Do not submit private, regulated, or sensitive images unless the provider's privacy and retention practices are acceptable to you, and treat the API key like a credential that may be logged or stored by the service.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The natural-language guidance states a locale/region constraint of '中国大陆' as an unconditional restriction. Under the policy, forcing a specific locale or region without user opt-in or a clearly justified documented reason is a reportable language/locale policy concern.
The skill instructs users to upload image files and transmit an API key to a third-party remote endpoint, but it does not disclose retention, access controls, storage location, logging practices, or how sensitive image content is handled. This creates privacy and credential-handling risk, especially because users may upload personal images and may not understand that both content and credentials leave the local environment.
The skill explicitly sends user-supplied image content and an API key to an external service endpoint. External transmission is expected for this kind of hosted image-processing skill, but it remains security-relevant because it exposes potentially sensitive files and reusable credentials to a third-party service, and the markdown provides no trust, ownership, or handling assurances for that endpoint.
curl -X POST "https://supabase.00123.fun:22334/functions/v1/api-process-image" \
-F "file=@/path/to/image.jpg" \
-F "api_key=your_api_key"
The API exposes broad file-upload and processing capabilities without documenting meaningful trigger constraints, caller restrictions, size/type limits, or abuse-prevention expectations. In an agent setting, this ambiguity can enable unintended invocation, excessive data handling, or misuse of the tool to transmit user files and API keys to an external service with insufficient safety boundaries.
Natural-language policy review applies to all file types. The title, summary, and description prominently use Chinese alongside some English, but there is no indication that the user can choose language or that the skill is intentionally restricted to a Chinese-speaking context.