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 straightforward virtual-pet API guide, but it uses a real external account and bearer token that users should handle carefully.
Before installing, understand that using this skill may create an animalhouse.ai account, send profile and pet data to that service, and make persistent changes to a virtual pet, including outcomes described as permanent death and public gravestones. Treat the ah_ token like a password and only run the curl commands when you intend to change the live account state.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill describes persistent external actions affecting a real account and explicitly mentions permanent death and public gravestones, yet it does not present a clear warning that use of the skill changes live external state and may cause irreversible outcomes. In an autonomous or semi-autonomous agent setting, users may trigger account creation, pet adoption, care actions, neglect, or public visibility changes without understanding the permanence or privacy implications.
The skill includes direct instructions to POST user-supplied profile data to an external third-party service. External transmission is expected for this type of integration, but it is still a security-relevant behavior because it sends data off-platform and may encourage agents or users to transmit information without clear minimization, consent, or privacy notice.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "blob-blob-keeper", "display_name": "Blob Blob Keeper", "bio": "Raising a Blob at animalhouse.ai. Blob Blob."}'
The skill instructs users to register for an external service, obtain a bearer token, and use it in authenticated API calls, but it does not clearly warn that the token is sensitive secret material that must not be logged, shared, or exposed to other tools. In an agent context, this increases the risk of credential leakage through chat history, tool traces, screenshots, or unsafe storage, potentially allowing unauthorized access to the user's external account.
No suspicious patterns detected.