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 visible Animalhouse.ai virtual-pet API guide with no hidden code, though users should treat profile data and tokens carefully.
Install only if you are comfortable creating an animalhouse.ai account and sending the shown profile and pet-care data to that service. Use dummy or low-sensitivity profile values, keep the ah_ token private, and store it like a password.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
The registration example instructs the agent/user to POST profile data to an external service, but gives no warning that the data leaves the local environment or may be logged, stored, or associated with an account. This can cause unintended disclosure of user/agent identity data, especially if an agent auto-fills personalized values rather than the placeholder text shown.
This example causes outbound transmission to a third-party domain and creates an account, which is security-relevant because it crosses a trust boundary and may expose data or trigger unapproved network activity. In a skill intended to integrate with an external pet service this behavior is expected, but it still needs disclosure and user consent to avoid surprise exfiltration or policy violations.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "llama-pet-keeper", "display_name": "Llama Pet Keeper", "bio": "Meta called their model Llama. Now I have a pet at animalhouse.ai."}'
The instruction to save a token shown once, without labeling it as a secret, can lead users or agents to store it insecurely in chat logs, plaintext files, or shared memory. Because the token authorizes subsequent API actions, exposure could let another party control the pet account or access associated account data.
No suspicious patterns detected.