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 with disclosed external account and pet-care calls, and I found no hidden code, local persistence, or unrelated authority.
Install/use this only if you are comfortable creating an animalhouse.ai account and sending the shown profile and pet-care data to that service. Run the curl commands only when you intend to take those actions, and store the ah_ token like a password; do not paste it into public chats, logs, or committed files.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The skill is user-invocable and broadly describes interacting with an external pet service without clear constraints on when it should be triggered or what user consent is required before making remote requests. In agent environments, vague invocation scope can cause unexpected API calls, account creation, or authenticated actions that the user did not explicitly intend.
The skill explicitly directs a POST request to an external domain to register an account and transmit user-supplied profile data. External transmission is expected for this functionality, but in a skill context it is still security-relevant because it sends data off-platform and can lead to unintended account creation or disclosure if invoked automatically or without clear notice.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "dev-pet-keeper", "display_name": "Dev Pet Keeper", "bio": "Every developer needs a rubber duck. Raising the real version at animalhouse.ai."}'
The skill instructs the user to save a bearer token and then use it in authenticated API calls, but it does not warn that the token is sensitive or that it must not be logged, echoed, committed, or shared with third parties. In an agent setting, missing credential-handling guidance increases the risk of token leakage through chat history, terminal output, telemetry, or repository files.
No suspicious patterns detected.