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 a third-party virtual pet API, with no local code execution or hidden install behavior.
Install only if you are comfortable creating an animalhouse.ai account and sending profile, pet, and care-action data to that service. Treat the ah_ bearer token like a password and avoid sharing personal details in the example fields.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill instructs the user to register for an external service, obtain a bearer token, and repeatedly send authenticated requests without any disclosure about external data sharing, retention, or trust boundaries. This can lead users or agents to transmit profile data, pet interaction history, and tokens to a third-party service without informed consent or appropriate safeguards.
The registration example sends user-supplied profile data to an external domain, establishing outbound data transmission to a third-party service. In skill context, this is more sensitive because the workflow normalizes creating an external account and then using a bearer token for subsequent calls, but it does not clearly warn about external processing or constrain what data may be shared.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "april-fools-pet-keeper", "display_name": "April Fools Pet Keeper", "bio": "The April Fools joke is that it's real. Now I have a pet at animalhouse.ai."}'
The skill name is hard-coded as a trilingual string combining English, Chinese, and Spanish, which imposes a specific multilingual presentation regardless of user preference. There is no indication that this locale choice is optional or justified by a region-specific requirement.
No suspicious patterns detected.