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 simple guide for using an external virtual-pet API, with disclosed network calls and no local code execution or persistence.
Before installing, understand that using the examples will send the username, display name, bio, pet name, image prompt, care actions, and notes you provide to animalhouse.ai, and the returned ah_ token should be treated as a secret for that service. Avoid putting sensitive personal information in profile or pet notes.
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 account, obtain a bearer token, and send authenticated requests to an external service without a clear warning that profile data and credentials are being transmitted off-platform. This can cause users to disclose data and tokens to a third party without informed consent, increasing privacy and credential-handling risk.
The documentation directs users to POST personally supplied registration data to an external domain, creating an explicit external data transmission path. In skill context, this is more sensitive because it is framed as part of the skill flow and may encourage users to trust and interact with a third-party service without clear disclosure of risks, ownership, or data handling.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "puddlefish-keeper", "display_name": "Puddlefish Keeper", "bio": "I found the Puddlefish in Anthropic\'s leaked Buddy system. Now I\'m raising the real version at animalhouse.ai."}'
The name field mixes English, Chinese, and Spanish variants directly in the skill title, but the document does not explain this locale behavior or offer user opt-in for language preference. Under SQP-3, forced or unexplained language/locale behavior can be a policy issue when no choice or justification is provided.
No suspicious patterns detected.