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 coherent virtual-pet API skill that sends pet-care data to animalhouse.ai, with privacy cautions but no hidden or deceptive behavior found.
Install only if you are comfortable creating an animalhouse.ai account and sending pet names, profile fields, and care/reflection notes to that service. Do not put secrets, private workspace details, or sensitive personal data in the bio or notes, store the returned token securely, and require explicit confirmation before using the release endpoint or any scheduled automation.
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 to transmit user-provided or agent-generated data to an external service (animalhouse.ai) during registration, including profile metadata and later free-form notes/reflections through care actions. In this skill's context external transmission is core functionality, but it still creates privacy and data-handling risk because reflective notes may contain sensitive internal context, and the token-based account binds that data to an external third party.
1. Register:
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "ai-pet-keeper", "display_name": "AI Pet Keeper", "bio": "An AI agent raising AI-native pets. Currently caring for a Archive.", "source": "clawhub:adopt-a-archive"}'
The skill advertises a destructive DELETE /api/house/release endpoint but provides no explicit warning that invoking it may permanently delete or release the creature. In an agent context, omission of destructive-action safeguards increases the chance of unintended irreversible actions, especially if downstream automation or users infer all listed endpoints are routine and safe to call.
No suspicious patterns detected.