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 is a disclosed barcode lookup integration that sends a user-provided barcode and API key to JisuAPI, with no evidence of hidden persistence, destructive actions, or unrelated data access.
Before installing, users should be comfortable sending queried barcode values and their JISU_API_KEY to JisuAPI and should monitor any provider quota or billing tied to that key. The skill is best used for explicit product barcode lookups, not barcode generation, QR handling, or general product search.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill metadata declares required environment access and, by implication, external API/network use, but the skill does not declare an explicit tool scope such as permissions or allowed-tools. This weakens least-privilege controls and can cause the runtime or reviewers to underestimate what the skill can access, especially since it uses an API key and makes outbound requests.
The activation text is broad enough that the agent may invoke this skill for loosely related requests about barcodes without strong boundaries. Because the skill performs external lookups using a configured API key, over-broad routing can trigger unnecessary data disclosure to a third-party service, wasted API quota, or unintended execution when the user did not clearly request barcode lookup.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
BARCODE2_URL = "https://api.jisuapi.com/barcode2/query"
def query_barcode(appkey: str, req: dict):
This Python file includes natural-language documentation and usage text in Chinese, with no indication that the skill is region-specific or that users may choose another language. The policy requires flagging language or locale constraints when they are imposed without opt-in or justification.
No suspicious patterns detected.