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 skill does what it says: it queries a disclosed third-party traffic restriction API using a user-provided city/date and API key.
Install only if you are comfortable using JisuAPI and sending the requested city/date plus your JISU_API_KEY to that service. Avoid entering unrelated personal information in queries, and review JisuAPI account terms, quota, and privacy expectations before use.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill declares environment-variable and implied network usage in metadata, but does not define an explicit tool scope such as allowed tools or permissions. That can weaken sandboxing and review controls by making external requests and secret access less transparent to the host and user, especially for a skill that depends on a third-party API key.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
VEHICLE_CITY_URL = "https://api.jisuapi.com/vehiclelimit/city"
VEHICLE_QUERY_URL = "https://api.jisuapi.com/vehiclelimit/query"
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
VEHICLE_CITY_URL = "https://api.jisuapi.com/vehiclelimit/city"
VEHICLE_QUERY_URL = "https://api.jisuapi.com/vehiclelimit/query"
The documentation describes the external JisuAPI backend, but it does not clearly warn end users that their query inputs will be transmitted to a third-party service. This creates a privacy and transparency issue because location/date requests and usage patterns may be shared off-platform without explicit user awareness.
This code file contains natural-language documentation exclusively in Chinese, including the skill description and API reference context. Under the policy, forcing a specific language without offering user opt-in or alternatives is a locale/language policy concern.
No suspicious patterns detected.