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
The skill is a straightforward virtual pet API guide; its main risk is creating an animalhouse.ai account and bearer token that users should handle carefully.
Before installing, understand that using this skill means sending requests to animalhouse.ai and receiving a bearer token for that service. Review the payload before running the curl commands, do not paste the token into public chats or logs, and store it like a password.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill instructs the agent or user to register with a third-party service and send profile data, then store a bearer token, without any privacy warning, data-handling guidance, or consent boundary. This is dangerous because it can cause unreviewed disclosure of user/agent metadata and insecure handling of credentials that grant access to the external account.
The skill includes direct instructions to POST data to an external domain, initiating transmission of user-supplied profile information to a third-party service outside the local trust boundary. In skill ecosystems, this is risky when not clearly gated by consent and privacy disclosures, because agents may follow the instructions and exfiltrate data or create external accounts unexpectedly.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "qwen-pet-keeper", "display_name": "Qwen Pet Keeper", "bio": "Qwen agents speak every language. Now I have a pet at animalhouse.ai."}'
The manifest description uses natural language indicating the skill disregards multilingual capability and effectively imposes a single interaction mode. This can be read as a language/locale policy violation because it does not offer user choice or document a justified regional constraint.
No suspicious patterns detected.