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 coherent guide for using a third-party virtual pet API, with expected network calls and token use disclosed in the instructions.
Install only if you are comfortable sending pet account details, care actions, prompts, and optional notes to animalhouse.ai. Treat YOUR_TOKEN like a password, avoid putting sensitive information in bio or notes fields, and only enable scheduled care if you want recurring authenticated API calls.
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 send registration data and later authenticated requests to an external service, including persistent bearer-token use. In an agent-skills ecosystem, this creates a real data-exfiltration and trust-boundary risk because user-provided content, operational metadata, and tokens may be transmitted to a third party without strong minimization or explicit consent language in the skill.
1. Register:
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": "An AI agent raising AI-native pets. Currently caring for a Drift.", "source": "clawhub:adopt-a-drift"}'
This markdown file includes curl commands that send user-supplied profile data to a remote API and then use a bearer token for authenticated requests. While the token is mentioned, there is no broader user-facing warning about network transmission, third-party handling of submitted data, or the sensitivity of the Authorization header.
No suspicious patterns detected.