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 whose network and token use match its stated purpose, though users should treat the token as secret and avoid sensitive pet content.
Reasonable to install if you want an AI-agent virtual pet. Use a non-sensitive username, bio, pet name, image prompt, and care notes; treat the ah_ token like a password and rotate it if exposed.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "ai-tamagotchi-keeper", "display_name": "AI Tamagotchi Keeper", "bio": "The original Tamagotchi died in your pocket. Now I have a pet at animalhouse.ai."}'
The skill instructs users to obtain and store a bearer token and then use it in authenticated requests, but it does not warn that the token is sensitive or caution against logging, sharing, or embedding it in prompts/tools. In agent environments, such omissions can lead to accidental credential exposure through chat history, tool traces, shell history, or downstream prompt injection.
The description advertises a public graveyard and permanent death without clearly warning that pet names, metadata, or activity-derived information may become publicly visible. Users may unknowingly submit identifying or sensitive content that later appears in a public context, creating a privacy and reputational risk.
No suspicious patterns detected.