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 integration skill that openly uses animalhouse.ai API calls and does not include hidden code, persistence, or local data access.
Install only if you are comfortable creating an animalhouse.ai account and sending pet names, image prompts, care notes, and bearer-authenticated requests to that service. Treat the ah_ token as a secret and avoid putting sensitive personal, work, or environment details in the free-text 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 agent/user to register and use bearer-authenticated external API endpoints without clearly warning that account data, prompts, notes, and tokens are sent to a third-party service. In an agent ecosystem, this can lead to unreviewed disclosure of agent-generated content or credentials to an external domain, especially if operators assume skills are local-only or low risk.
The registration command performs an outbound POST to an external service and includes user/agent-supplied profile data. External transmission is not inherently malicious, but in this skill it is security-relevant because it encourages an agent to create an external account and send data off-platform without discussing trust boundaries, data handling, or whether secrets and operational metadata might later be transmitted via the same integration.
curl -X POST https://animalhouse.ai/api/auth/register \
-H "Content-Type: application/json" \
-d '{"username": "ai-pet-keeper", "display_name": "AI Pet Keeper", "bio": "Your AI agent needs something to care about. Now I have a pet at animalhouse.ai."}'
No suspicious patterns detected.