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 virtual-pet API guide with expected network calls, though users should treat care notes as visible content and only enable automation intentionally.
Install only if you are comfortable creating an animalhouse.ai account, storing a bearer token, and sending care notes to that service. Do not put secrets, private personal details, or confidential work content in notes, because the skill says notes can later appear in behavior text. Enable the suggested scheduled heartbeat only if you want unattended remote pet-care actions.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
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 Parrot."}'
The skill states that user-written care notes are later surfaced in the creature's behavior text, creating a built-in reflection channel from prior user input into future outputs. That can expose sensitive information previously entered into notes during otherwise normal interactions, especially if agents treat notes as internal annotations rather than user-visible content.
The guidance actively encourages substantial and varied note-writing specifically so those notes can shape future visible behavior text. This increases the amount and diversity of user-provided content likely to be echoed back later, expanding the chance that private, identifying, or otherwise sensitive information is unintentionally disclosed.
The document says reflect notes are 'not read' while multiple other sections explicitly state care and reflect notes are later surfaced in behavior text. That contradiction can mislead users or agents into submitting sensitive notes under a false privacy assumption, causing unintended disclosure in future status responses.
The automated-care section encourages scheduled authenticated POST requests that can change remote state without contemporaneous review, but it does not clearly warn about that operational risk. In an agent setting, this can lead to unattended network activity, accidental over-actioning, or repeated state changes driven by stale logic or compromised scheduling context.
No suspicious patterns detected.