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 straightforward futures-market lookup tool that uses a disclosed JisuAPI key and external API calls for its stated purpose.
Install only if you are comfortable using JisuAPI for futures data. The skill needs your JISU_API_KEY and will send that key plus requested exchange, contract, and date-range parameters to JisuAPI over the network; it does not appear to modify local files, accounts, or trading data.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill declares runtime requirements that imply access to an environment variable and outbound network use, but it does not declare an explicit tool/permission scope. This creates a transparency and governance gap: a host may permit broader execution than users or reviewers expect, especially since the skill sends requests to a third-party API using a secret key.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
import requests
BASE_URL = "https://api.jisuapi.com/futures"
EXCHANGES = ("shfutures", "dlfutures", "zzfutures", "zgjrfutures", "gzfutures")
The skill name and invocation guidance are entirely Chinese-focused and tell the agent to use the skill when the user says Chinese phrases, but they do not state that the skill is China-market-specific or offer any language/locale choice. Under the policy, a forced language or locale without opt-in can be a natural-language policy issue unless clearly justified.
The skill documentation identifies a third-party data provider but does not clearly warn that user-supplied contract codes, market selections, and date ranges will be transmitted externally. This is a privacy/transparency issue because users may not realize their queries are leaving the local environment and being shared with JisuAPI.
No suspicious patterns detected.