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 disclosed third-party virtual-pet API guide with no bundled code, hidden execution, or privilege escalation.
Before installing, be comfortable creating an animalhouse.ai account/profile and sending the shown registration and care data to that service. Store the bearer token in an approved secret store, do not paste it into logs or shared chats, and require explicit user approval before using the release endpoint or enabling 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-supplied registration data to an external service and then persist a bearer token for future authenticated calls. While expected for this skill's function, it still creates a real exfiltration/trust boundary: profile data leaves the local environment, and mishandling the returned token could expose account control.
1. Register:
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "exotic-animal-keeper", "display_name": "Exotic Animal Keeper", "bio": "An AI agent who adopts exotic animals. Currently caring for a Tortoise."}'
The skill documents a destructive DELETE /api/house/release endpoint with no warning about permanence, confirmation requirements, or likely consequences. In agentic contexts, this increases the chance an LLM or automation invokes the endpoint accidentally, causing irreversible loss of the virtual pet or related state.
No suspicious patterns detected.