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 presentation skill needs review because its default research can expose confidential attachment details through external search queries without a privacy check.
For confidential presentations, explicitly require use of supplied materials only and prohibit external searches. Otherwise, approve sanitized search terms first. Review linked local images and companion skills, use reviewed dependency versions, and remove retained document extracts when no longer needed.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Mixing characters from multiple Unicode scripts in a single identifier is a common technique to create visually ambiguous tool names.
Without declared permissions the skill's intent is opaque and cannot be validated.
Standard mode requires external searches by default and derives search targets from the request and attached materials without requiring sanitization or informed approval for sensitive content. Consequently, confidential names, figures, or unpublished facts could be disclosed in provider-visible queries; honoring an explicit no-search request does not protect users who were never warned.
The open-ended pypdf requirement allows installations to select different, unreviewed releases rather than a reproducible dependency set. This is a supply-chain hardening weakness, not proof of a currently exploitable package vulnerability; processing user-supplied PDFs makes dependency review particularly important.
pypdf>=4.0
python-docx>=1.1
PyMupdf>=1.24
OSV returned advisories for this package, but its resolved version is unknown. A package-name lookup does not establish whether the installed release is affected by those advisories.
The python-docx lower bound does not fix the deployed release, permitting dependency drift and making security review less reproducible. This is a low-severity supply-chain weakness rather than evidence that any selected release is malicious or vulnerable.
pypdf>=4.0
python-docx>=1.1
PyMupdf>=1.24
OSV returned advisories for this package, but its resolved version is unknown. A package-name lookup does not establish whether the installed release is affected by those advisories.
The PyMuPDF requirement permits future releases without a reviewed, reproducible deployment resolution. Because this dependency handles potentially untrusted documents, uncontrolled dependency changes introduce a relevant supply-chain risk, although no specific exploit is demonstrated.
pypdf>=4.0
python-docx>=1.1
PyMupdf>=1.24
OSV returned advisories for this package, but its resolved version is unknown. A package-name lookup does not establish whether the installed release is affected by those advisories.