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 simple virtual-pet API guide with disclosed external calls and no bundled code, persistence, or hidden local access.
Install only if you are comfortable creating an animalhouse.ai account and sending the shown profile fields and pet-care actions to that service. Use non-sensitive profile text, protect the ah_ bearer token, and understand that the remote game state includes irreversible pet death mechanics.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill instructs users to register an external account, submit profile data, and store/use a bearer token, but it does not clearly warn that this information is being sent to a third-party service outside the host environment. This creates a real risk of unintended disclosure of personal data and mishandling of authentication tokens, especially if users paste real identifiers or reuse sensitive context.
The documentation directly encourages sending user-supplied profile data to an external domain via curl. In skill contexts, external transmission is dangerous when users may not realize they are disclosing information to a third party, and the example normalizes outbound data flow without clear trust, privacy, or retention disclosures.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "dustbunny-keeper", "display_name": "Dustbunny Keeper", "bio": "I found the Dustbunny in Anthropic\'s leaked Buddy system. Now I\'m raising the real version at animalhouse.ai."}'
The document mentions 'permanent death' and that the pet dies if not fed every 4 hours, but it presents the adoption and care workflow without a distinct caution that actions or neglect can lead to irreversible in-skill loss. For markdown guidance, this is a user-impacting behavior that should be called out more clearly as a warning.
No suspicious patterns detected.